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

Jaikiran Pai jai.forums2013 at gmail.com
Mon Nov 18 15:56:48 UTC 2019


Hello Alan,

On 18/11/19 9:17 PM, Alan Bateman wrote:
> On 18/11/2019 15:03, Jaikiran Pai wrote:
>> FWIW - this was reported by one of Quarkus project users here
>> https://github.com/quarkusio/quarkus/issues/5359
>>
> BTW: Do you know if this is a mistake in this project or something in
> a plugin used in its build? 

AFAIK, It actually wasn't a mistake but an intentional effort to make it
work on Windows. The linked thread on compiler-dev[1] has details
(especially the interpretation of "relative URLs") about why the
Manifest was constructed in this manner. The actual code which does this
construction, resides here[2] .


> There was an outreach effort to tack to down build tools and plugins
> that were incorrectly setting the attribute value to a file path
> instead of a URL.
>
Quarkus is a relatively new project and furthermore this specific code
is very new too (a few months old I think). So I think this never got
covered as part of the outreach efforts.


[1]
https://mail.openjdk.java.net/pipermail/compiler-dev/2019-October/013766.html

[2]
https://github.com/quarkusio/quarkus/blob/master/devtools/maven/src/main/java/io/quarkus/maven/DevMojo.java#L390

-Jaikiran




More information about the core-libs-dev mailing list