Closed jamezp closed 2 weeks ago
Thank you for the report. Indeed, something is wrong. I don't know yet what is wrong in our configuration. We use a combination of mrjar-gradle-plugin with Gradle toolchains. If you have any clue whether we are doing something wrong, feel free to comment here or open a PR. I will be away for a week, but once I'm back I'll investigate if there are no ideas in the meantime.
No worries. For my specific case I was able to easily workaround it. I'm not too familiar with Gradle TBH, but if I find some time I can have a look.
The
META-INF/versions
are used for Multi-Release JAR's. It looks this project produces an MR JAR for 9 and 21. However, in both cases the class has a bytecode level of Java 1.8, which doesn't seem right.As you can see the byte code version is 52 which is Java 1.8. This is causing an issue with the
maven-site-plugin
.Expected Behavior
The byte code version should match the version being targeted.
Actual Behavior
The byte code version is 52.0.
Steps to Reproduce
Compile project and check the files generated in the
META-INF/versions
directory. What I did was run:Your Environment
Currently using reactor-core 3.6.6, but downloaded 3.6.7 and noticed the same issue.
netty
, ...): N/Ajava -version
): Java 21uname -a
):Linux 6.9.4-200.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Jun 12 13:33:34 UTC 2024 x86_64 GNU/Linux