Hi,
Here is the list of plugins that aren’t
singleton in Papyrus main [1]
Also the extract from OSGI norm for
singleton [2]
IMHO: We should only have singleton in
Papyrus.
Is there any use case in Papyrus
context where no-singleton plugin may be interesting?
Is there a reason for these plugins not
having the singleton=true parameter?
Regards,
Benoît
1:
org.eclipse.papyrus.emf.facet.util.pde.core
org.eclipse.papyrus.emf.facet.util.ui
org.eclipse.papyrus.emf.facet.util.jface.ui
org.eclipse.papyrus.emf.facet.widgets
org.eclipse.papyrus.infra.core.log
org.eclipse.papyrus.infra.tools
org.eclipse.papyrus.uml.appearance
org.eclipse.papyrus.eclipse.project.editors
org.eclipse.papyrus.uml.xtext.integration.core
org.eclipse.papyrus.uml.modelexplorer.widgets
org.eclipse.papyrus.uml.profile.newchildmenu.generator
org.eclipse.papyrus.uml.profile.drafter.documentation
2:
singleton
-
Indicates that the bundle can only have a single version
resolved in an environment.
A value of
true
indicates
that the bundle is a
singleton
bundle. The
default value is
false. The
Framework
must resolve at most one bundle when multiple versions of a
singleton bundle with
the same
symbolic name are installed. Singleton bundles do not affect
the resolution of non-singleton
bundles
with the same symbolic name.