Bug 129595

Summary:	[Commands] handlers: overrideActionId from legacy extensions
Product:	[Eclipse Project] Platform	Reporter:	Douglas Pollock <douglas.pollock>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	eclipse, prakash
Version:	3.2
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:
Bug Blocks:	129591

Description Douglas Pollock

2006-02-27 11:15:29 EST

Need to decide on a policy for handling overrideActionId from legacy action-based extensions.

Comment 1 Michael Van Meekeren

2006-04-21 13:21:09 EDT

Moving Dougs bugs

Comment 2 Paul Webster

2007-03-15 20:17:41 EDT

We've pretty well decided that this idea won't be in the new API, and we will just need to make sure our legacy converter can handle it.
PW

Comment 3 Paul Webster

2007-04-09 19:34:17 EDT

These seem like RetargetActions poor cousin for popup menus.  With limited conversion in 3.3 we can look at this in 3.4
PW

Comment 4 Paul Webster

2009-03-02 11:40:07 EST

Updated as per http://wiki.eclipse.org/Platform_UI/Bug_Triage
PW

Comment 5 Paul Webster

2009-09-09 14:29:28 EDT

I'd like to look at this as a last piece of the legacy object contributions to commands work.

PW

Comment 6 Eclipse Webmaster

2019-09-06 15:30:03 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

Comment 7 Eclipse Webmaster

2019-09-06 15:37:02 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.