Community
Participate
Working Groups
I am working on migrating the project to Java11 and Eclipse 2020-03. In one of the modules a call is been made like IWorkbenchPage p = JavaPlugin.getActivePage(); and this gives the below mentioned error. !ENTRY org.eclipse.ui 4 0 2020-12-17 12:14:09.771 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/ui/JavaPlugin I have included the plugin entry in my Manifest.mf and have re-verified that the class is present in the plugin org.eclipse.jdt.ui_3.21.0. It is also present in the classpath. Also, to check I have added the Accessible permission to the plugin but still nothing works. I am unable to identify why is eclipse not able to read this particular class and I am stuck. Am I missing something ? Any suggestion is welcome.
I would check whether the OSGi console shows your plugin and 'org.eclipse.jdt.ui' in the RESOLVED/STARTED state when you start up your application. An INSTALLED state would usually indicate there are resolution errors. If you're running your application as a child of the main Eclipse (using "Eclipse Application" run configuration) you can usually see it from the dropdown entries in the Console View. If running Eclipse from commandline you can usually try supplying '-noexit -console' to connect to it. 'ss' to the state of a bundle, and 'diag ${id}' to diagnose a bundle based on its id. https://www.ibm.com/developerworks/library/os-ecl-osgiconsole/index.html is pretty old but still relevant. Is the NoClassDefFoundError the only error ? In some cases a failure for a class to evaluate its static members (or maybe have its activator start correctly?) will result in subsequent NoClassDefFoundError.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
