No thanks to the followers of this blog... as if there are any... but I was able to overcome the classpath issue that had stumped me for a few days.
It turns out that if an eclipse plugin wraps a jar library, it can not deploy as an uber-jar if you want other plugins to be able to access classes within the wrapped jar library. The plugin must be deployed as an exploded directory (at least on Eclipse 3.3 & 3.4). This is quite odd and non-intuitive, but that's the way it is.
If anyone knows another way around this, please comment.
Subscribe to:
Post Comments (Atom)
Posts
No comments:
Post a Comment