On 12/9/19 12:17 PM, Jonathan Gibbons wrote:
I note that javac now uses the same definition of tryResolveFile in
its handling of Class-Path manifest entries, and so the behavior for
the compiler and runtime should now be aligned.
Yay!
This patch looks good to me.
Mandy
-- Jon
On 12/09/2019 12:10 PM, Brent Christian wrote:
Hi,
As discussed[1] last month on this alias, JAR Class-Path entries[2]
that encode an absolute Windows path (including a drive letter, so
e.g. "/C:/path/to/file.jar") are ignored as of 8211941.
Such entries are legal relative URLs, and should not be ignored.
Please review my fix to correct this.
Issue:
https://bugs.openjdk.java.net/browse/JDK-8235361
Webrev:
http://cr.openjdk.java.net/~bchristi/8235361/webrev06-open/
Thanks,
-Brent
1.
https://mail.openjdk.java.net/pipermail/core-libs-dev/2019-November/063491.html
2.
https://docs.oracle.com/en/java/javase/13/docs/specs/jar/jar.html#class-path-attribute
