Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 317338 - [model explorer] Should use the eclipse commands API rather than providing its own actionHandler framework
Summary: [model explorer] Should use the eclipse commands API rather than providing it...
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Camille Letavernier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 334984
Blocks:
  Show dependency tree
 
Reported: 2010-06-18 16:55 EDT by Cedric Dumoulin CLA
Modified: 2015-04-24 08:49 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 Cedric Dumoulin CLA 2010-06-18 16:55:17 EDT 
The Model Explorer provides a framework to register actions shown in its contextual menu. 
This is redundant with the Eclipse command framework (org.eclipse.ui.command).
Actually, it is only used from the controlmode plugin.
Is this additional framework really needed ?
If not, I propose to remove it and use the org.eclipse.ui.command instead.
Comment 1 Emilien Perico CLA 2010-06-30 03:41:02 EDT 
mark extension point as deprecated to avoid developer to use it
Comment 2 Camille Letavernier CLA 2012-09-12 09:06:25 EDT 
The control mode handlers have been refactored; the extension point doesn't seem to be used anymore in Papyrus.

I will remove it in 0.10 (Kepler).
Comment 3 Camille Letavernier CLA 2015-04-24 08:49:00 EDT 
The ModelExplorer properly relies on org.eclipse.ui.* extension points

I close the task