| Classpath in Run-time workbench [message #120331] |
Tue, 02 September 2003 06:13  |
Eclipse User |
|
|
|
Originally posted by: lists.luebken.spamremove.com
Hi
I still have some problem with the manifest.
I have created 2 plugins (plugin-a and plugin-b) where plugin-b requires
plugin-a and imports it. Plugin-b uses needs some classes from the jar
file from plugin-a. So I need to export the library.
Well that is true if I'm starting the platform through an ant script
but if I'm starting it through Run >> Run As >> Run-time workbench ,
it seems to ignore the export definition of the libraries.
So even if I'm exporting nothing out of plugin-a, plugin-b runs
perfectly fine while running through the "run-time-workbench".
My guess is that if a plugin requires the other plugin, it can read
everything if started through eclipse.
* So my question is:
How is the runtime classpath handled, while running through
"run-time-workbench" ?
* And is there anyway to enforce the use of the export tags?
Matt
PS: I think this is a pde issue, but noone answered on the pde mailing-list.
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02093 seconds
Home