RFR 8235361 : JAR Class-Path no longer accepts relative URLs encoding absolute Windows paths (e.g "/C:/...")

Jaikiran Pai jai.forums2013 at gmail.com
Sat Dec 21 05:22:03 UTC 2019

Thank you all for the real quick fix for these 2 issues.

In the context of Quarkus project, trying to get a decent workaround to
get past these issues across all prominent Java versions (and OS) was
starting to get a bit out of hand. But with this fixed consistently
within in the JDK now, it's much more comforting that the workarounds
that we have put in place in Quarkus won't need to last too long.


On 10/12/19 1:47 AM, 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.
> -- 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

More information about the core-libs-dev mailing list