Community
Participate
Working Groups
It seems extensions to "org.eclipse.ui.menus" that contribute to "popup:org.eclipse.debug.ui.DebugView" are ignored with platform version 4.13. I first noticed that the CDT reverse debugging commands were missing. Those have quite complex logic controlling visibility, but it looks like nothing contributed using "org.eclipse.ui.menus" and menuContributions make it to the menu with 4.13. The example below works fine with 4.12 and earlier. I haven't checked all entries in the menu, but so far, the only things I find that do make it into the menu are done using deprecated action based mechanisms. <menuContribution locationURI="popup:org.eclipse.debug.ui.DebugView?before=stepGroup"> <command style="toggle" commandId="XXX"> <visibleWhen checkEnabled="true"/> </command> </menuContribution> <extension point="org.eclipse.ui.commands"> <command id="XXX" categoryId="YYY" description="ZZZ" name="AAA"> </command> </extension> <extension point="org.eclipse.ui.handlers"> <handler commandId="XXX" class="BBB"> <enabledWhen> <with variable="org.eclipse.core.runtime.Platform"> <test property="org.eclipse.core.runtime.bundleState" args="CCC" value="ACTIVE"/> </with> </enabledWhen> </handler> </extension>
I have not seen any issues with JDT Debug, moving to CDT for further analysis.
This is not a CDT problem. The plugin.xml below, along with an empty handler implementation, will give you a "Command" item in the Debug View on Eclipse platform versions < 4.13 and nothing in 4.13: * plugin.xml: <?xml version="1.0" encoding="UTF-8"?> <?eclipse version="3.4"?> <plugin> <extension point="org.eclipse.ui.commands"> <command id="com.example.plugin.command" defaultHandler="com.example.plugin.Handler" name="Command"> </command> </extension> <extension point="org.eclipse.ui.menus"> <menuContribution locationURI="popup:org.eclipse.debug.ui.DebugView?before=stepGroup"> <command commandId="com.example.plugin.command"/> </menuContribution> </extension> </plugin> * com/example/plugin/Handler.java: package com.example.plugin; import org.eclipse.core.commands.AbstractHandler; import org.eclipse.core.commands.ExecutionEvent; import org.eclipse.core.commands.ExecutionException; public class Handler extends AbstractHandler { public Object execute(ExecutionEvent event) throws ExecutionException { return null; } }
(In reply to Sarika Sinha from comment #1) > I have not seen any issues with JDT Debug, moving to CDT for further > analysis. @Sarika - As Mattias has provided an example in Comment 2 that is not CDT dependent, I think this belongs in Platform. I remain on the CC list, please let me know what CDT can do beyond Mattias' minimal test case.
Created attachment 280388 [details] Example project contributing "Command" to context menu in Debug view I've created a project out of comment 2. I guess we broke something in menu managers again.
Reminds me of bug 550986.
Please retarget if you still plan to fix this for 4.14.
Simeon, we should address this for 4.15, especially if this affects CDT debugging.
I no longer see the problem with latest 4.14 and the attached example: https://bugs.eclipse.org/bugs/attachment.cgi?id=280388 I do see the problem in 4.14 m1. I no longer see the problem when I manually add this commit on top: https://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?id=7efdf6755aefe96cd46a578e0b0a65b9ea44a2b2 So I think this is fixed with the fix for bug 552361. Hi Mattias Bertilsson, could you re-test with the latest 4.14 build? E.g.: https://download.eclipse.org/eclipse/downloads/drops4/I20191204-1800/ Best regards and thanks, Simeon
Thanks Simeon, closing. @Matthias, feel free to reopen if you still can reproduce with 4.14 RC2.
I tested with 4.14RC2a-201912100 and it looks ok.