Custom Commands don't appear to work in Eclipse Juno / 4.2 #19

ziesemer opened this Issue Aug 10, 2012 · 4 comments

2 participants


When trying to execute any custom command (including the ones supplied by default), nothing happens - but the following is logged to the Eclipse error log:

Failed to execute item de.bastiankrol.startexplorer.customCommand034

org.eclipse.core.commands.NotHandledException: There is no handler to execute for command de.bastiankrol.startexplorer.customCommand034
    at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(
    at org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(
    at org.eclipse.ui.menus.CommandContributionItem.access$19(
    at org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(
    at org.eclipse.swt.widgets.EventTable.sendEvent(
    at org.eclipse.swt.widgets.Widget.sendEvent(
    at org.eclipse.swt.widgets.Display.runDeferredEvents(
    at org.eclipse.swt.widgets.Display.readAndDispatch(
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(
    at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(
    at org.eclipse.ui.internal.Workbench$
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(
    at java.lang.reflect.Method.invoke(
    at org.eclipse.equinox.launcher.Main.invokeFramework(
    at org.eclipse.equinox.launcher.Main.basicRun(

Eclipse build 20120614-1722, Windows 7 SP1 x64, Java 1.7.0_05 64-bit.


Thanks for the report. I just downloaded the Juno release and can reproduce the bug. It seems, StartExplorer custom commands are not compatible with Juno. I have not yet investigated this in detail but I will try to have a look at it as soon as possible.


I did a little more digging/debugging. The handler is clearly attached to the command but the Eclipse Juno code ignores that and tries to get a handler by some lookup algorithm which I do not really understand. To me this looks like a bug. On the other I, I use some Eclipse infrastructure which is marked with something like "plug-in imlementors should not use it, it's Eclipse-internal stuff" - so this might be the problem. I'm pretty sure this not has not been there when I first implemented the custom command feature (a few years ago).

I'll try to clarify this, but I guess it will take a while.


Has been fixed in version 1.2.1.

Mark, could you please take a moment and verify the fix?

@basti1302 basti1302 was assigned Aug 17, 2012

Confirmed fixed. Thanks!

@ziesemer ziesemer closed this Aug 17, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment