| exporting plugin reveals classpath problems [message #187499] |
Fri, 26 November 2004 19:49 |
Eclipse User |
|
|
|
I am building an RCP plugin on windows using eclipse 3. To make my jar
files visible to the project, I am following the advice of the RCP
newsgroup and putting them all in a separate plugin, exporting the jars
and listing this as a dependent plugin for my main plugin. This appears
to work fine because I get no compilation errors in the eclipse
environment. However, now when I export these 2 plugins I am not getting
what I expect: The main plugin won't export at all. From the package
explorer, I am doing a rt-click on the plugin, export, Deployable plugins
and fragments, and then selecting my 2 plugins from the list of available
plugins and fragments. I am deploying as a directory structure. The
export process exports the plugin with the jar files, and then stops on
the main plugin. This main plugin has errors with imports that would
never compile without the proper classpath. For instance, I am getting an
error with
import net.sf.hibernate.HibernateException;
The class with this import does not complain in the eclipse environment,
so why is it complaining all of a sudden when I am trying to export?
|
|
|
Powered by
FUDForum. Page generated in 0.23275 seconds
Home