You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2016/08/23 14:15:46 UTC

[Bug 60033] Jar scanning not handling properly Manifest class-path attribute

https://bz.apache.org/bugzilla/show_bug.cgi?id=60033

Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from Mark Thomas <ma...@apache.org> ---
(In reply to Olivier Peyrusse from comment #0)

> 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.

It is generally a good idea to do a little research before raising a bug. [1]
would have been informative.

Bug 59961 does look as if it would be useful to you. Patches (attached to that
bug) welcome.

[1]
https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath

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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org