On Tue, Oct 30, 2018 at 05:41:42PM +0100, Thorsten Glaser wrote:
> Doko, we need a fix for this for openjdk-8 at least
> (openjdk-10 users can just upgrade to 11 which doesn’t
> exhibit those problems), kinda urgently.
This is an intentional upstream change
| Improved Validation of Class-Path Attribute in JAR File Manifest (core-libs)
|
| The JAR file specification states that URLs in the Class-Path manifest
attribute must be relative,
| though this has not been enforced. To better conform to the JAR
specification, absolute URLs
| (those that include a scheme) are now ignored. For JAR files not loaded from
the file system,
| Class-Path entries navigating to a parent directory (using "../") are also
ignored.
|
| Applications depending on a JAR file loaded from an absolute URL element
specified in
| Class-Path attribute may encounter a ClassNotFoundException. The historical
behavior can be
| restored by setting a new system property,
jdk.net.URLClassPath.disableClassPathURLCheck
| to true. Debugging info for Class-Path entries that are ignored can be
printed to stderr by
| setting -Djdk.net.URLClassPath.disableClassPathURLCheck=debug.
When/if this is reported/fix in src:surefire, we can release an update for it.
Cheers,
Moritz
