[Bug 59226] StandardJarScanner ignores jars in manifest Class-path header

2016-09-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59226 --- Comment #16 from Mark Thomas --- See bug 59961 -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat

[Bug 59226] StandardJarScanner ignores jars in manifest Class-path header

2016-09-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59226 --- Comment #15 from Mauro Molinari --- I think I also encountered this problem after deploying in Tomcat 8.5.5 a webapp previously run in Tomcat 8.0.14. I have a lot of WARNING: file not found for JARs mentioned in useless Class-Path entries i

[Bug 59226] StandardJarScanner ignores jars in manifest Class-path header

2016-08-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59226 --- Comment #14 from saschakarc...@gmx.de --- I totally agree that this double negation would be confusing. Unfortunatelly jarsToSkip and does not help in that case, because at least one of the JARs contains TLDs (Which I do want to be scanned

[Bug 59226] StandardJarScanner ignores jars in manifest Class-path header

2016-08-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59226 --- Comment #13 from Mark Thomas --- I haven't checked the code but you might be able to use jarsToSkip or a JarScanFilter to not scan them. Failing that, a new enhancement request to make the manifest processing option sounds reasonable. I'd

[Bug 59226] StandardJarScanner ignores jars in manifest Class-path header

2016-08-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59226 --- Comment #12 from saschakarc...@gmx.de --- Just found an interesting problem: We're trying to migrate a bunch of webapps from tomcat 7 to 8.5.4 with the goal in mind not to change too much. Our Tomcat has got a whole bunch of 3rd party librar

[Bug 59226] StandardJarScanner ignores jars in manifest Class-path header

2016-05-04 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59226 --- Comment #11 from Ignacio del Valle Alles --- Thank you -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr..

[Bug 59226] StandardJarScanner ignores jars in manifest Class-path header

2016-05-04 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59226 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 59226] StandardJarScanner ignores jars in manifest Class-path header

2016-05-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59226 --- Comment #9 from Ignacio del Valle Alles --- I see. I'll think about it to too. Can you give more details on these minor bugs? -- You are receiving this mail because: You are the assignee for the bug. -

[Bug 59226] StandardJarScanner ignores jars in manifest Class-path header

2016-05-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59226 --- Comment #8 from Mark Thomas --- Update. I've spent a fair amount of time looking at the proposed patch to see if there is a way to avoid processing a JAR once to look at the class path and again to scan it. I think it is possible but it is

[Bug 59226] StandardJarScanner ignores jars in manifest Class-path header

2016-04-29 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59226 --- Comment #7 from Ignacio del Valle Alles --- Just added a new PR on GitHub. Basically what it does is from the jar url returned by a url class loader start a DFS traversal over the graph of related jars (the relation is transitive) -- You

[Bug 59226] StandardJarScanner ignores jars in manifest Class-path header

2016-04-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59226 --- Comment #6 from Ignacio del Valle Alles --- (In reply to Mark Thomas from comment #4) > (In reply to Ignacio del Valle Alles from comment #3) > > Hi Mark, this problem comes for system (application) class loader, that is > > responsible of

[Bug 59226] StandardJarScanner ignores jars in manifest Class-path header

2016-04-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59226 --- Comment #5 from Mark Thomas --- Hint: Rather than inferring the JARs added to the class path via one or more manifests, process the manifests and determine the JARs that have been added. -- You are receiving this mail because: You are the

[Bug 59226] StandardJarScanner ignores jars in manifest Class-path header

2016-04-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59226 --- Comment #4 from Mark Thomas --- (In reply to Ignacio del Valle Alles from comment #3) > Hi Mark, this problem comes for system (application) class loader, that is > responsible of handling class-path entries, not returning manifest jar url

[Bug 59226] StandardJarScanner ignores jars in manifest Class-path header

2016-04-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59226 --- Comment #3 from Ignacio del Valle Alles --- Hi Mark, this problem comes for system (application) class loader, that is responsible of handling class-path entries, not returning manifest jar urls when executed as java -jar. If there is a p

[Bug 59226] StandardJarScanner ignores jars in manifest Class-path header

2016-04-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59226 --- Comment #2 from Mark Thomas --- Notes: - The web application class loader will ignore any Class-Path entries in a manifest. - Any class loader above that (common, server, shared, etc.) will process Class-Path entries for any JAR on the clas

[Bug 59226] StandardJarScanner ignores jars in manifest Class-path header

2016-03-23 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59226 Ignacio del Valle Alles changed: What|Removed |Added OS||All --- Comment #1 from Igna