5.11.4 on maven central has module-info.class version 53; should be max 52

[Alex-K37]

Steps to reproduce

> jar -x -f ~/.m2/repository/org/junit/jupiter/junit-jupiter-api/5.11.4/junit-jupiter-api-5.11.4.jar
> ll
total 4
drwxr-xr-x 2 x users 107 Feb  1  1980 META-INF
-rw-r--r-- 1 x users 578 Feb  1  1980 module-info.class
drwxr-xr-x 3 x users  19 Feb  1  1980 org
> file module-info.class 
module-info.class: Cafe Babe compiled Java class data, version 53.0

[sormuras]

The lowest Class File version a module-info.class can have is 53, as observed by you. Module descriptors were introduced by Java 9:

Java 8 | 52.0
Java 9 | 53.0

When the JAR is loaded by a Java 8 runtime, that compiled module descriptor file is usually never touched by code in Java 8 runtimes.

In the light of this, I close the issue as invalid.

[Alex-K37]

Thank you for the quick check upon this issue.

The issue occures with a special type of Java 8 compiler which apparently loads all .class files from JAR and, consequently, fails.

Even if this behaviour may be somewhat peculiar, it does not seem to be too far fetched a presumption that a JAR file claiming Java 8 compatibility should contain .class files of matching compatibility, only.

Just my 2 cents... I admit I am not completely up-to-date with respect to compatibility issues of JARs.

Dropped back to 5.11.3, successfully. Not reopening.

[sormuras]

[...] special type of Java 8 compiler [...]

Which one?

[marcphilipp]

Dropped back to 5.11.3, successfully. Not reopening.

How does that help? 5.11.3 also contains a module-info.class file with byte code version 53.

[Alex-K37]

Re. the compiler: unable to disclose.

Somehow, it did "instantly" work with 5.11.3 - the maven pom is quite unstable (and non-standard, testing) at present, though. I did not check the contents of the JAR. After your comment I switched back to 5.11.4 and now it also works with 5.11.4. Maybe a wrong classpath slipped in at that point...

Apologies, and thank you both for assisting!