| Summary: | [WorkbenchLauncher] Errors: Bad extension specification, and, startup class must implement org.eclipse.ui.IStartup | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Simon Archer <sja.eclipse> | ||||
| Component: | UI | Assignee: | Boris Bokowski <bokowski> | ||||
| Status: | RESOLVED DUPLICATE | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | 3.2 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Simon Archer
Created attachment 38197 [details]
Example
Looking at the description for the org.eclipse.ui.startup extension point I see the following that implies that the nested <startup> element (that defines a class implementing IStartup) is optional. "If the startup element has a class attribute, the class will be instantiated and earlyStartup() will be called on the result. Otherwise, this method will be called on the plug-in class." Once I added a <startup> element the messages written to the .log go away. I would rather that the <startup> element is optional. But perhaps all of this is just weaknesses in the documentation of the org.eclipse.ui.startup extension point. It's a weakness in the documentation that I fixed recently. See bug 128178 comment 14. *** This bug has been marked as a duplicate of 128178 *** |