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

Bug 334984

Summary:	[General] Papyrus should use the eclipse UI commands/menu/toolbars API rather than providing its own framework
Product:	[Modeling] Papyrus	Reporter:	Cedric Dumoulin <cedric.dumoulin>
Component:	Core	Assignee:	Project Inbox <mdt-papyrus-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:
Bug Depends on:	334262
Bug Blocks:	317338, 336518

Description Cedric Dumoulin

2011-01-21 04:43:55 EST

Papyrus should use the Eclipse UI commmands/menu/toolbars API rather than providing its own API.
All Papyrus plugins should use this API to provide new menu/toolbars/contextual menu...
Plugins providing menu entry point should document them, and provides associated IDs.

The extensions points to use for declaring UI commands:
org.eclipse.ui.commands
org.eclipse.ui.handlers
org.eclipse.ui.menus

Eclipse Documentation:
- Platform Plug-in Developer Guide > Programmer's Guide > Plugging into the workbench > Basic workbench extension points using commands

Comment 1 Mathieu Velten

2011-02-14 05:21:23 EST

This has been fixed in rev 4018.

Comment 2 Mathieu Velten

2011-02-14 05:23:34 EST

reopen the bug since I am guessing it is not specific to navigation and some non standard menus are still there, please close it if not.

Comment 3 Camille Letavernier

2014-03-25 15:42:54 EDT

Almost everything is now using org.eclipse.ui.* extension points.

Specific subtasks should be opened when this is not the case

I close this one