--- Thomas DeWeese <[EMAIL PROTECTED]> wrote:
I don't know anything about how JEdit does it thing, but is it possible that the way it sets up the class path 'partitions' the class loaders in some way? So batik-bridge.jar can see batik-util.jar but not the other way round (a bit like the UNIX link line).
Hmmm. I bet it must be an issue with some kind of custom class loading. When jEdit loads a plugin, class library dependencies are done by putting the jars in a standard "jars" directory (the same one with the actually plugin jar). When jEdit starts up, it goes through this directory and loads what it needs. You get a message on the jEdit activity log that it scanned the jars.
In particular, I bet they aren't actually on the classpath.
Hmm you might try making the following change in batik.bridge.Messages
< new LocalizableSupport(RESOURCES); -- > new LocalizableSupport(RESOURCES, Messages.class.getClassLoader());
I'd be interested to see if that fixes it...
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]