Bug 98912 - [ActionSets] Invalid Menu Extension (Path is invalid)
Summary: [ActionSets] Invalid Menu Extension (Path is invalid)
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-06-08 07:38 EDT by Gary Karasiuk CLA
Modified: 2005-06-08 10:25 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gary Karasiuk CLA 2005-06-08 07:38:59 EDT
In 3.0.2, I was able to have one plug-in add menu items to another plug-in's
menu.

Here is a fragment from the plug.xml of the plug-in that is being extended:

   <extension  point="org.eclipse.ui.actionSets">
      <actionSet label="%ActionSet.label" visible="true"
id="org.eclipse.perfmsr.ui.actions">
         <menu
               label="%Menu.label"
               id="org.eclipse.perfmsr.menu">
            <separator name="snapshots"></separator>
            <separator  name="all"></separator>
            <separator  name="other"></separator>
<!-- This group can be extended by other plugins. -->
            <separator name="additions"></separator>
         </menu>

And here is a fragment from the plugin.xml that is trying to add some
additional menu items:

         <action
               label="%OpenSnapshots.label"
               tooltip="%OpenSnapshots.tootip"

class="org.eclipse.perfmsr.ui.client.OpenSnapshotsViewActionDelegate"
               menubarPath="org.eclipse.perfmsr.menu/additions"
               id="org.eclipse.perfmsr.ui.client.opensnapshotsview">
         </action>

In 31RC1 I now get:

Invalid Menu Extension (Path is invalid):
org.eclipse.perfmsr.ui.client.opensnapshotsview
Comment 1 Nick Edgar CLA 2005-06-08 10:25:15 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 ***