On Thu, 14 Nov 2024 11:57:52 GMT, Christian Stein <cst...@openjdk.org> wrote:
> Please review this change ensuring all targeted classes in a MR-JAR file > should target the same or a lower classfile version. > > For example, having compiled source files with `javac` 25 without using the > `--release` option (or with `--release 25`) and trying to archive them via a > `jar --create --file a.jar --release 9 ... --release 10 ...` command now > fails with: > > classfile release value of META-INF/versions/9/version/Version.class too > high: 25 > classfile release value of META-INF/versions/10/version/Version.class too > high: 25 > invalid multi-release jar file a.jar deleted > > > This pull request contains fixes to existing tests which produced invalid > MR-JAR files. Most of those fixes are achieved by adding an appropriate > `--release N` option to the associated `javac` call. One of those fixes > rewrites the classfile version bytes between the `javac` and `jar` calls. I was wondering if this would have to be covered in the jar file spec, but it looks like it already is: https://docs.oracle.com/en/java/javase/23/docs/specs/jar/jar.html#multi-release-jar-files > A class file under a versioned directory, of version N say, in a > multi-release JAR must have a class file version less than or equal to the > class file version associated with Nth major version of a Java platform > release. ------------- PR Comment: https://git.openjdk.org/jdk/pull/22103#issuecomment-2538703496
