Class-Path (in jar file) semantics different between Java 11 and 13 (on Windows)?

[Alan Bateman]

On 18/11/2019 15:01, Jaikiran Pai wrote:
> :
>
> So this Class-Path entry is being ignored starting Java 13.
>
Yes, bad values are now ignored, bringing an end to an effort on the 
run-time over multiple releases to fix the problems this area. 
JDK-8224253[1] is the JDK 13 release note to announce this change and I 
see you've found the system property that you can use to track down bad 
values. In previous releases you will get the same behavior with 
-Djdk.net.URLClassPath.disableClassPathURLCheck=false as the changes to 
reject bad input have been in place for some time. Brent can summarize 
but I think the only outstanding work is to fix the javac handling.

-Alan
[1] https://bugs.openjdk.java.net/browse/JDK-8224253