Bug 98061 - [RCP] Invalid Menu Extension
Summary: [RCP] Invalid Menu Extension
Status: RESOLVED DUPLICATE of bug 36389
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Linux
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Nick Edgar CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 98071 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-06-02 04:48 EDT by jernej srebrnic CLA
Modified: 2005-06-03 10:02 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 jernej srebrnic CLA 2005-06-02 04:48:15 EDT
On the new build I20050527-1300 our RCP application looses some menu entrys.
Invalid Menu Extension (Path is invalid): ...action_id...

but not all. On build eclipse-SDK-I20050513-1415 it works normaly (no
warnings).
Any idea. All actions seem to be done in the same way using plugin.xml

LINUX and WINDOWS
Comment 1 DJ Houghton CLA 2005-06-02 06:13:41 EDT
*** Bug 98071 has been marked as a duplicate of this bug. ***
Comment 2 DJ Houghton CLA 2005-06-02 06:14:40 EDT
Please include the full log file and attach your sample plug-in, if able.
Comment 3 Nick Edgar CLA 2005-06-02 11:52:59 EDT
Yes, need to know which items it's complaining about.
Also, are these for your app's actions, or are extra unwanted IDE plug-ins
getting included in your config (most of them expect the IDE menu structure)?
Comment 4 jernej srebrnic CLA 2005-06-03 05:02:27 EDT
Strated working agein in N20050506-0010...

Comment 5 jernej srebrnic CLA 2005-06-03 07:03:02 EDT
The two referd action are one liners.( wizard.open()..). The toolbar
contribution works normaly for bouth plugins...

Edited xml files:
1.  menu separators 
<?xml version="1.0" encoding="UTF-8"?>
<?eclipse version="3.0"?>
<plugin>

   <extension
         point="org.eclipse.ui.actionSets">
      <actionSet
            label="Administrator"
            visible="true"
            id="....administrator.actionSet">
         <menu
               id="administracija"
               label="Administracija">
            <separator name="administracijaSeparator"/>
            <separator name="uporabnikiSeparator"/>
            <separator name="praviceSeparator"/>
         </menu>
      </actionSet>
   </extension>
</plugin>

2. not working entry in second plugin
<?xml version="1.0" encoding="UTF-8"?>
<?eclipse version="3.0"?>
<plugin>
   <extension
         point="org.eclipse.ui.actionSets">
      <actionSet
            id=".....administrator.praviceobdelave.analitik.actionSet"
            label="Analitske obdelave"
            visible="true">
         <action             
class="....administrator.praviceobdelave.analitik.actions.AnalitskeObdelaveAction"
               id="...administrator.praviceobdelave.action.analitik"
               label="Analitske obdelave"
               menubarPath="administracija/administracijaSeparator"
               style="push"/>
      </actionSet>
   </extension>

</plugin>

3. working entry
<?xml version="1.0" encoding="UTF-8"?>
<?eclipse version="3.0"?>
<plugin>
   <extension
         point="org.eclipse.ui.actionSets">
      <actionSet
            id=".....administrator.procesi.actionSet"
            label="Procesi "
            visible="true">
         <action
               class="...administrator.procesi.actions.ProcesiAction"
               icon="%action.procesi.icon"
               id=".....administrator.procesi.actions.procesi"
               label="%action.procesi.label"
               menubarPath="administracija/administracijaSeparator"
               style="push"
               toolbarPath="administracija/administracijaSeparator"
               tooltip="%action.procesi.label"/>
      </actionSet>
   </extension>

</plugin>

Comment 6 Nick Edgar CLA 2005-06-03 10:02:10 EDT
This looks like a dup of bug 36389, which is still an issue in 3.1.
Basically 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.


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