ClassNotFoundException - Using PDE Tools generated Ant build.xml [message #583366] |
Thu, 23 October 2008 15:03 |
John Rodriguez Messages: 8 Registered: July 2009 |
Junior Member |
|
|
I have been developing a debugger and editor. I have used Eclipse to debug
problems by startig an Eclipse Application. All classes load correctly.
I then used the PDE Tools to generate an Ant build file.
Plugin.xml -> PDE Tools -> CreateAnt Build File
This generates a build.xml. I then run Ant with the build.xml to generate
my plugin jars using the targets build.jars and build.update.jar
When I add the 2 jars to Eclipse in the plugin directory, I get the
following error when trying to start the editor:
Could not open the editor: The editor class could not be instantiated.
This usually indicates a missing no-arg constructor or that the editor's
class name was mistyped in plugin.xml.
java.lang.ClassNotFoundException: luaeditorideplugin.LuaEditor
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl assInternal(BundleLoader.java:481)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:397)
...
I do have a no-arg constructor:
public LuaEditor() {
STUFF DELETED
}
I also notice that Eclipse is able to successfully find my images for the
editor which are in the jar. The file is displayed under the project with
the correct image.
I looked at the jar file created by build.xml and all the classes are
under the "bin" folder.
bin/luaeditorideplugin/LuaEditor.class
bin/ ...
However, when I looked at the standard Eclipse editors in
org.eclipse.ui.editors_3.4.0.v20080603-2000.jar, the classes are at the
top level:
org/eclipse ...
Is having the bin folder as the top level the problem?
Do I have to include something else in the Manifest to indicate that
classes are in bin?
I did not see a way to specify in the plugin.xml Build tab that bin should
not be included?
Thanks,
John Rodiguez
|
|
|
Powered by
FUDForum. Page generated in 0.02894 seconds