this has not been fixed in Debian, it affects openjdk-8 and openjdk-10 there.
As far as has been analysed to date, this is caused by a new, stricter, JAR check that went from OpenJDK to Debian/*buntu’s Java 10 and 8 (but not Debian’s Java 11), missing that the new check should be disabled by default (probably “for now”).
There, we’re trying to get the maven-surefire-plugin working with the new stricter check. It only hits Debian/*buntu for now, but given that the new check exists upstream (even if disabled for now), it’ll eventually hit everyone.
Hi Martijn,
this has not been fixed in Debian, it affects openjdk-8 and openjdk-10 there.
As far as has been analysed to date, this is caused by a new, stricter, JAR check that went from OpenJDK to Debian/*buntu’s Java 10 and 8 (but not Debian’s Java 11), missing that the new check should be disabled by default (probably “for now”).
See also: https:/ /issues. apache. org/jira/ browse/ SUREFIRE- 1588
There, we’re trying to get the maven-surefire- plugin working with the new stricter check. It only hits Debian/*buntu for now, but given that the new check exists upstream (even if disabled for now), it’ll eventually hit everyone.