Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 323440 - [CommonNavigator] navigatorContent extension point causing implementer's plugins to get loaded sooner then expected
Summary: [CommonNavigator] navigatorContent extension point causing implementer's plug...
Status: CLOSED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact: Francis Upton IV CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-23 16:45 EDT by Ian Tewksbury CLA
Modified: 2010-10-07 08:13 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Tewksbury CLA 2010-08-23 16:45:50 EDT 
While investigating Bug 316796 I discovered that the JSDT plugins will load in a blank workspace with the resource view being the default view when Eclipse is opened.  It seems this is happening because the Project Explorer view is loading any plugin that implements the org.eclipse.ui.navigator.navigatorContent plugin even though there is nothing to display in the Project Explorer.

It would be great if the JSDT plugins were not forced to load until the navigatorContent extension defined in the JSDT plugins was actully needed. i.e. when there was a project in the workspace that met the triggerPoint definition in the JDT navigatorContent extension implementation.
Comment 1 Ian Tewksbury CLA 2010-08-23 16:56:09 EDT 
Corrections
(In reply to comment #0)
> While investigating Bug 316796 I discovered that the JSDT plugins will load in
> a blank workspace with the resource view being the default view when Eclipse is
> opened.  It seems this is happening because the Project Explorer view is
> loading any plugin that implements the
> org.eclipse.ui.navigator.navigatorContent plugin even though there is nothing

should read "...the org.eclipse.ui.navigator.navigatorContent extension..."

> to display in the Project Explorer.
> 
> It would be great if the JSDT plugins were not forced to load until the
> navigatorContent extension defined in the JSDT plugins was actully needed. i.e.
> when there was a project in the workspace that met the triggerPoint definition
> in the JDT navigatorContent extension implementation.

This should have been "JSDT" not "JDT"
Comment 2 Ian Tewksbury CLA 2010-08-31 10:54:21 EDT 
*** Bug 316796 has been marked as a duplicate of this bug. ***
Comment 3 Ian Tewksbury CLA 2010-10-06 17:04:12 EDT 
Turns out the JSDT trigger point is wrong.
Comment 4 Nitin Dahyabhai CLA 2010-10-06 21:16:06 EDT 
(In reply to comment #3)
> Turns out the JSDT trigger point is wrong.

Can you open a bug report in JSDT with details?
Comment 5 Ian Tewksbury CLA 2010-10-07 08:13:04 EDT 
(In reply to comment #4)
> (In reply to comment #3)
> > Turns out the JSDT trigger point is wrong.
> 
> Can you open a bug report in JSDT with details?

It already exists. Bug 316796.