| Summary: | [misc] Remove or reduce JSDT startup impact | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] JSDT | Reporter: | Ian Tewksbury <itewksbu> | ||||
| Component: | General | Assignee: | Ian Tewksbury <itewksbu> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Nitin Dahyabhai <thatnitind> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | browe, cmjaun, deboer, melickm | ||||
| Version: | 3.2 | Keywords: | performance | ||||
| Target Milestone: | 3.2.3 | Flags: | thatnitind:
review+
|
||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Ian Tewksbury
This is actually caused by a CommonNavigator problem, dupping against a bug against that component. *** This bug has been marked as a duplicate of bug 323440 *** Turns out there is an issue with the JSDT trigger point which we inherited from JDT. Created attachment 180692 [details]
Fix Patch
Fixes the org.eclipse.ui.navigator.navigatorContent extension point enablement clauses so that JSDT does not get activated until it needs too.
Right now this extension point causes the JSDT plugins to load as soon as the workspace loads. These changes fixes it so the JSDT plugins do not load until a project that uses JSDT exists in the workspace.
Committed, thanks, Ian! |