> On Nov 19, 2019, at 3:22 PM, David Lloyd <david.ll...@redhat.com> wrote: > > On Mon, Nov 18, 2019 at 9:37 AM Alan Bateman <alan.bate...@oracle.com> wrote: >> >> 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 > > Where can the updated specification be found? It has in the past been > clearly specified and well understood that class path entries are > interpreted as relative URLs. If that has changed then this will > definitely break Quarkus and perhaps other applications as well. > > A Google search for "JAR file specification" only seems to turn up > older versions (JDK 10 and earlier).
https://docs.oracle.com/en/java/javase/13/docs/specs/jar/jar.html > -- > - DML > <http://oracle.com/us/design/oracle-email-sig-198324.gif> <http://oracle.com/us/design/oracle-email-sig-198324.gif> <http://oracle.com/us/design/oracle-email-sig-198324.gif> <http://oracle.com/us/design/oracle-email-sig-198324.gif>Lance Andersen| Principal Member of Technical Staff | +1.781.442.2037 Oracle Java Engineering 1 Network Drive Burlington, MA 01803 lance.ander...@oracle.com <mailto:lance.ander...@oracle.com>
