Markus KARG wrote on Wednesday, September 20, 2006 9:28 AM: >>> That's wrong. Maven automatically creates the correct Class-Path >>> attributes in the manifest, and it's up to the fop team to decide >>> what third party library versions to use. >>> >>> >> >> No! If any library would declare a Class-Path in its deps, > you could nearly use none in combination. Just because you > can Maven configure to generate it, it is not said that it > makes any sence. The classpath entry are useful for jars that > behave as applications, but not for libraries that are > suppoed to be used by applications. >> >> > Actually you can use it because the classes in the Class-Path entry of > one jar will be taken into account only by fop. If you have other libs > that need other versions, those can use them since the > Class-Loader-Hierarchy will take respect of that (if not, it is a bug > in the JRE).
Then all the Sun JRE's are buggy. Sorry, I am using exactly this artifact for a long time now without ever noticing that weird classpath entry. The only time it is respected is when you start the jar as app: java -jar my.jar In this case your classpath theory applies. The situation is different on app servers though ... but far from consistent. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
