Bug 103203 - [ActionSets] Invalid Menu Extension (Path is invalid) when menus are defined in another plugin
Summary: [ActionSets] Invalid Menu Extension (Path is invalid) when menus are defined ...
Status: RESOLVED DUPLICATE of bug 36389
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Nick Edgar CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-08 15:33 EDT by Scott Delap CLA
Modified: 2005-07-11 12:58 EDT (History)
0 users

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 Scott Delap CLA 2005-07-08 15:33:20 EDT 
I've see this logged before but it seems as if no one wants to fix it or doesn't
care so I'll log it again with the hope it is fixed.  I'm trying to contribute
to the search menu from another plugin.  I receive this error:

Invalid Menu Extension (Path is invalid)

The only work around seems to be to redefine the menu in the action set which is
a bad hack in my opinion.  Things worked fine in the 3.1 MX builds but not in
the 3.1 RC builds or now with the official 3.1 release.
Comment 1 Kim Horne CLA 2005-07-09 17:12:22 EDT 
What other bugs are you referring to?
Comment 2 Nick Edgar CLA 2005-07-11 12:58:58 EDT 
An action set A can't refer to a menu defined in another action set B
(even if they're in the same plug-in), since A may be visible and B not visible.

The workaround is to define exactly the same <menu> element in all action sets
that add to it.

You may have been getting lucky in 3.0.x, but this has never been supported.


*** This bug has been marked as a duplicate of 36389 ***

*** This bug has been marked as a duplicate of 36389 ***