-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greg Johnson wrote: | Thanks Andrew. Someone on FedoraForum.org is starting to help shed a little light on the problem. He noticed a problem in the manifest of tomcat5's bootstrap.jar file. | In the manifest he noticed this line: | Class-Path: jmx.jar commons-daemon.jar commons-logging-api-1.1.1.jar tomcat-juli.jar | | As a workaround, he executed this: | ln -s commons-logging-api.jar commons-logging-api-1.1.1.jar This is why classpaths in manifests are a bad idea. How easy was it to find that? And any upgrade of commons-logging would break tomcat5 even though the two packages are unrelated. | This workaround is less involved than combining the contents of two jar files. | | I went looking for the same problem in tomcat6. However the manifest in bootstrap.jar doesn't even have a Class-Path element. I would say that an incorrect classpath is wrong (and should even be removed), but an empty classpath is not. While I am not sure if the fault lies with tomcat or eclipse, the eclipse plugin should place a symlink where it expects to find its libraries, so in that sense it's a packaging bug in the eclipse plugin. - -- Sincerely, David Walluck <david@xxxxxxxx> -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org iEYEARECAAYFAkg3F2kACgkQItObMyg2XCV7IgCeO4mr6IObgugSDNUtVmjT+2Bi E30AnjEhc/426Do0dZXtaF/JtTHfG4QM =yCZq -----END PGP SIGNATURE----- -- fedora-devel-java-list mailing list fedora-devel-java-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-java-list
