| Eclipse 3.0 ClassLoader problem [message #259360] |
Wed, 07 July 2004 14:45  |
Eclipse User |
|
|
|
This is Eclipse 3.0 final on MacOS (I've seen the smae thin on Linux
with RC7 as well though).
I've got an application with 2 plugins, A and B, with B depending upon
A. My plugin.xml file for plugin A explicitly exports 3 packages. When I
try to execute an action declared in plugin B it fails to run, altering
the code slightly to use dynamic class loading (Class.forName()) shows
that the cause is a ClassNotFoundException.
I'm not using manifest.mf or anything funky like that.
Has anybody got any ideas as to what could be causing this? Is there a
way of telling from the configuration (via some PDE tool maybe) which
classes are visible?
Cheers,
Ian.
--
#ifndef __COMMON_SENSE__ | Ian Phillips
#include <std_disclaimer> | http://ianp.org
#endif
|
|
|
|
| Re: Eclipse 3.0 ClassLoader problem [message #259954 is a reply to message #259573] |
Thu, 08 July 2004 22:19  |
| Eclipse User |
|
|
|
I've made some progress. It seems that there's a problem with the way my
plugin.xml (not using manifest.mf any more) files have been created.
They were created under an older RC (5 or 6, I forget) and imported from
version to version. Building a trivial test app with 3.0 final doesn't
exhibit this problem.
I'm going to try recreating all of my plugins in final, and importing
just the classes from my old workspace and hopefully that will fix it.
As a general note, upgrading eclipse from one version to the next seems
to be very painful. I think that this is something which should be
considered for future (3.x series) releases.
Cheers,
Ian.
--
#ifndef __COMMON_SENSE__ | Ian Phillips
#include <std_disclaimer> | http://ianp.org
#endif
|
|
|
Powered by
FUDForum. Page generated in 0.03209 seconds
Home