Run-time Workbench error

[Brian]

I am new to Eclipse and SWT, and I keep running into a classpath problem...
I'm doing a project where I am using SWT widgets to display data from a custom Java data object. The problem I have is this- in the design view, Eclipse can see my custom data class and access its methods, etc. When I run my project as a Java Application, it works fine too. But I am trying to make it a Plug-in now, and when I test it on the Run-Time workbench, I get a NoClassDefFound error as soon as I instantiate an object from my data class. I have tried several different ways to tell the Run-Time workbench the path to my data class, and it is on the Java build path of my Plug-in code- so what can I do to make the Run-Time workbench find my class??

Thanks for any help you can give me.

[Eric Clayberg]

I'm doing a project where I am using SWT widgets to display data from a custom Java data object. The problem I have is this- in the design view, Eclipse can see my custom data class and access its methods, etc. When I run my project as a Java Application, it works fine too. But I am trying to make it a Plug-in now, and when I test it on the Run-Time workbench, I get a NoClassDefFound error as soon as I instantiate an object from my data class. I have tried several different ways to tell the Run-Time workbench the path to my data class, and it is on the Java build path of my Plug-in code- so what can I do to make the Run-Time workbench find my class?

Generally, questions like this should be posted to the Eclipse platform newsgroup. That said, it sounds like you just need to include a reference to your JAR file in your plugin manifest file (plugin.xml). If your plugin does not compile, that is a .classpath problem. If it fails to run, that is a plugin.xml problem.

[Brian]

Generally, questions like this should be posted to the Eclipse platform newsgroup. That said, it sounds like you just need to include a reference to your JAR file in your plugin manifest file (plugin.xml). If your plugin does not compile, that is a .classpath problem. If it fails to run, that is a plugin.xml problem.

Sorry about that, and thanks for the help! Adding the JAR to the plugin.xml did the trick.