Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 363448 - Bad uses of the "org.eclipse.ui.startup" extension point
Summary: Bad uses of the "org.eclipse.ui.startup" extension point
Status: CLOSED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.8.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Camille Letavernier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-10 05:27 EST by Alain Le Guennec CLA
Modified: 2013-05-31 10:05 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 Alain Le Guennec CLA 2011-11-10 05:27:50 EST 
There are several occurrences of bad use of the "org.eclipse.ui.startup" extension point.
The documentation of that extension point specifically warns against using the Activator of the plugin as the explicit class to be activated early, otherwise the Activator gets instantiated twice (once for early activation and one for normal activation). Instead, either the class to be instantiated should be distinct from the Activator, or it should be left implicit in which case the Activator is considered automatically (deprecated usage, though, or so it seems).
I found several occurrences in Papyrus where the Activator class of a plugin is explicitly used for early activation, which indeed causes duplicated instantiations of the Activator class.
The following plugins are concerned:
-org.eclipse.papyrus.diagram.menu
-org.eclipse.papyrus.modelexplorer
-org.eclipse.papyrus.sysml.modelexplorer
-org.eclipse.papyrus.uml.menu
-org.eclipse.papyrus.uml.modelexplorer
Comment 1 Camille Letavernier CLA 2013-05-31 10:05:04 EDT 
Fixed (See Bug 406508)