tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 60033] New: Jar scanning not handling properly Manifest class-path attribute
Date Tue, 23 Aug 2016 14:09:01 GMT

            Bug ID: 60033
           Summary: Jar scanning not handling properly Manifest class-path
           Product: Tomcat 8
           Version: 8.5.4
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Util

Running tomcat 8.5.4 on a maven project with various jars, I ended up with a
lot of errors like:
> WARNING: Failed to scan [file:/home/olivier/maven/repo/net/sf/jung/jung-graph-impl/2.0.1/jung-api-2.0.1.jar]
from classloader hierarchy
> /home/olivier/maven/repo/net/sf/jung/jung-graph-impl/2.0.1/jung-api-2.0.1.jar
(No such file or directory)
> ... (stacktrace)

After some debugging, I discovered that it occurs for jars having a Manifest
file with a non-empty Class-Path attribute.

For example, jung-graph-impl-2.0.1.jar MANIFEST defines Class-Path as:
> Class-Path: jung-api-2.0.1.jar collections-generic-4.01.jar
With that, the code
(org.apache.tomcat.util.scan.StandardJarScanner#processManifest) tries to load
the jars as if located in the same directory, resulting in requests for
which does not exist.
Indeed, following maven guidelines, it is located in

As I am not familiar with MANIFEST, I don't know if the error comeo from a
badly defined MANIFEST, or if the manifest can reference jars outside this jar.

If Issue 59961 was complete, I could have skipped Manifest, as I don't need

Thanks for the reply

You are receiving this mail because:
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message