https://bz.apache.org/bugzilla/show_bug.cgi?id=59961
Bug ID: 59961
Summary: Provide an option to disable processing of Class-Path
entry in a jar's manifest file
Product: Tomcat 8
Version: 8.5.x-trunk
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P2
Component: Util
Assignee: dev@tomcat.apache.org
Reporter: saschakarc...@gmx.de
Scenario:
You want to add a JAR to the common (or shared) classloader which does contain
a manifest file refering to other JARs in it's class-path entry. These
referenced other JARs are not required for the application and thus are not
stored on the server.
When tomcat is started method "processManifest" of class
"org.apache.tomcat.util.scan.StandardJarScanner" tries to resolve that
class-path entry and you end up with lots of errors in the log.
Unfortunatelly you are not able to use the "jarsToSkip" and "<JarScanFilter>"
config params since this JAR actually contains one or more TLDs which should be
scanned.
Suggested "Improvement":
Provide a switch for not processing the class-path entry of manifest files.
Default would be TRUE (i.e. class-path entry is respected).
--
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
