https://bz.apache.org/bugzilla/show_bug.cgi?id=60033
--- Comment #2 from Olivier Peyrusse <kineol...@gmail.com> --- (In reply to Mark Thomas from comment #1) > Bug 59961 does look as if it would be useful to you. Patches (attached to > that bug) welcome. As stated by my comment, I read that task for improvement, but saw no attachement. As suggested by the comment, I was also investigating the usage of JarScanFilter. However, I have another question for you. Does the Manifest processing works for Tomcat in its embedded version ? When my issue occurs, the server I have was created by instanciated a Tomcat class (https://tomcat.apache.org/tomcat-8.0-doc/api/org/apache/catalina/startup/Tomcat.html), as well as no web.xml but instead WebAppInitializer class. In its application version, a WAR is loaded, containing in the lib folder all jars. Thus, looking for jars referenced by the Manifest in the same folder as the jar itself seems logical. This is different in my case, where the server is created from the main method, because the classpath of the program is made from several locations. If I reuse my example with jung-graph, it gives me: E.g. java -cp /home/olivier/maven/repo/net/sf/jung/jung-api/2.0.1/jung-api-2.0.1.jar;/home/olivier/maven/repo/net/sf/jung/jung-graph-impl/2.0.1/jung-graph-impl-2.0.1.jar MyMainClass In this case, jung-api-2.0.1.jar is indeed in the classpath, but not in the same folder as jung-graph-impl-2.0.1.jar. Maybe I am misusing the Tomcat class, but I heavily looked for a documentation or tutorial on how to use it, and found very few. Regards -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
