Community
Participate
Working Groups
Build Identifier: M2010211-1343 The "Run As" "Debug As" "Profile As" menu item appeared the first time the Project Explorer's context menu was shown and thereafter, it did not show. I found a link that matched my exact problem http://www.sigasi.com/content/run-menu-item-strangely-disappearing-context-menu#comments In my case, I wanted to not have the "Run As" "Debug As" "Profile As" to display at all so I tried the solution as one user commented in the above link: I have an RCP application which was showing exactly the same behavior. However I wanted that the Run As menu never show up because my application doesn't need it. I managed to do that by setting the debug plugins to load on startup by updating my runtime configuration. So I changed the org.ecliopse.debug.ui to a auto-start of true which did fix the problem of the "Run As" "Debug As" "Profile As" not displaying on the context menu. However, I do not want org.eclipse.debug.ui to be set to auto-start of true and feel this is not a good solution. The determination as to whether these menu items appear should be implemented so the org.eclipse.debug.ui does not have to be auto-start true if you don't want the menu items to appear at all. Reproducible: Always Steps to Reproduce: 1.Set up a RCP application 2.Display the context menu from Project Explorer 3.Run As menu item appears 4.Select context menu again 5.Run As menu item is not shown
Created attachment 189942 [details] Archive Zipped file - exported General Project I have attached an exported zipped file that contains a simple General Project in which this problem occurs.
Have you tried defining a capability and filtering out the menu contribution that way?
Defining a capability where?
(In reply to comment #3) > Defining a capability where? In your product (org.eclipse.ui.activities). I actually don't know a whole lot about it except that we use it in our product to filter out some of the UI contributions which are not relevant for us.
Thanks...will do that.
I'm marking as won't since we can't fix this without activating the debug plugins early.