Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 277183

Summary:	org.eclipse.team.core gets initialized even when there are no open projects
Product:	[Eclipse Project] Platform	Reporter:	Dan O'Connor <dan_o'connor>
Component:	Team	Assignee:	Platform Team Inbox <platform-team-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	dan_o'connor, pwebster, raji, Szymon.Brandys
Version:	3.5
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Dan O'Connor

2009-05-20 14:20:30 EDT

Build ID: 20090513-1800

Steps To Reproduce:
In Eclipse close all projects in the workspace.
Exit/Close Eclipse.
Launch Eclipse using the -console option
When Eclipse has finished initializing type the following in the console:

status org.eclipse.team.core

Notice that the plugin/bundle is active? When the workspace has no open projects is it possible for this plugin to not activate?



More information:

Comment 1 Szymon Brandys

2009-05-21 08:22:59 EDT

I can see two places activating org.eclipse.team.core. First is Rules in org.eclipse.core.resources another one is LightweightDecoratorDefinition in ui.workbench.

Comment 2 Dan O'Connor

2009-05-21 09:54:42 EDT

Basically our product is very sensitive to performance and plug-in start-up. Is there any way to prevent this plug-in from starting if all projects are closed? I had over looked the need for applying a decorator to a closed project, so if this is really needed please close out.
Thanks.

Comment 3 Eclipse Webmaster

2019-09-06 15:33:10 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

Comment 4 Eclipse Genie

2022-02-15 18:08:32 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.