Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 347008 - [General] AbstractCommandHandler should be in org.eclipse.core
Summary: [General] AbstractCommandHandler should be in org.eclipse.core
Status: NEW
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-24 11:43 EDT by Mathieu Velten CLA
Modified: 2017-09-08 09:53 EDT (History)
6 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 Mathieu Velten CLA 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 CLA 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 CLA 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 CLA 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...)