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

Bug 347008

Summary:	[General] AbstractCommandHandler should be in org.eclipse.core
Product:	[Modeling] Papyrus	Reporter:	Mathieu Velten <mathieu.velten>
Component:	Core	Assignee:	Project Inbox <mdt-papyrus-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	cletavernier, mathieu.velten, Patrick.Tessier, sebastien.gerard, vincent.lorenzo, yann.tanguy
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Mathieu Velten

2011-05-24 11:43:59 EDT

what do you think about moving this class from modelexplorer in org.eclipse.core ?
it doesn't depend on anything else and could then be used in plugins without depending on the model explorer.

As an example there is the org.eclipse.papyrus.uml.menu plugin that depends of modelexplorer because of that while it is not really necessary.
I want to use it in controlmode plugin but I don't want to depend of modelexplorer.

Comment 1 Mathieu Velten

2011-05-24 11:48:46 EDT

A copy of this class also exists in uml.modelexplorer and sysml.modelexplorer.
I really don't see the point of that since it is available in modelexplorer which is a dependency, I am guessing it is the consequence of some refactoring.

Comment 2 Yann Tanguy

2011-05-30 10:52:45 EDT

I'd prefer you leave {oep}.uml.modelexplorer and  {oep}.sysml.modelexplorer as is until the release (bug fixes are welcome but not refactoring for now).

Comment 3 Camille Letavernier

2013-07-05 11:06:05 EDT

This class has been duplicated in 4 plug-ins. The 4 classes now have different implementations.

None of these implementation seems valid (Deprecated code, rely on Active editor, or memory leaks...)