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

Bug 363448

Summary:	Bad uses of the "org.eclipse.ui.startup" extension point
Product:	[Modeling] Papyrus	Reporter:	Alain Le Guennec <alain.leguennec>
Component:	Core	Assignee:	Camille Letavernier <cletavernier>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	eclipse-bugzilla, vincent.lorenzo, yann.tanguy
Version:	0.8.1
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Alain Le Guennec

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

2013-05-31 10:05:04 EDT

Fixed (See Bug 406508)