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).That's wrong. Maven automatically creates the correct Class-Path attributes in the manifest, and it's up to the fop team to decide whatthird 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.
begin:vcard fn:Markus KARG n:KARG;Markus org:QUIPSY QUALITY GmbH;Entwicklung / R & D adr:;;Stuttgarter Strasse 23;Pforzheim;Baden-Wuerttemberg;75179;Bundesrepublik Deutschland email;internet:[EMAIL PROTECTED] title:Staatl. gepr. Inf. tel;work:+49-7231-9189-52 tel;fax:+49-7231-9189-59 note:QUIPSY(R) Entwicklung / R & D x-mozilla-html:TRUE url:http://www.quipsy.de version:2.1 end:vcard
smime.p7s
Description: S/MIME Cryptographic Signature
