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

[Brent Christian]

On 11/18/19 7:36 AM, Alan Bateman wrote:
 >
> 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.

Right, the "jdk.net.URLClassPath.disableClassPathURLCheck" system 
property can be used to once again allow bad values (though I believe it 
must be set to "true").

> Brent can summarize 
> but I think the only outstanding work is to fix the javac handling.

That's a good summary. :)  It's the only planned change I'm aware of.

It should be expected, however, that the disableClassPathURLCheck system 
property will be removed in a future release.

-Brent