-
Notifications
You must be signed in to change notification settings - Fork 827
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Massive jump from Java 8 to requiring Java 17 in a patch release (5.6.0 -> 5.6.1) #1134
Comments
My personal recommendation is to use the maven toolchains plugin to ensure the correct Java versions are used. As you can see in this demonstrator project I created a while ago you can run the maven under Java 21 (so you can us all modern plugins) and still run the actual Java 8 (or which ever you want) compiler to build the code. This also shows how you can then run integration tests under several different JDK versions. https://github.com/nielsbasjes/ToolChainsInCiBuilds |
Thanks for reporting this! I'm not sure how this happened. I guess one of the Maven Plugin updates is responsible. We are currently using I will look into this and release a new version asap. |
I just released 5.6.2. Again, thanks for reporting this so quickly. |
Yes, my build passes again with this version. |
Describe the bug
With the update from 5.6.0 to 5.6.1 there is a massive jump in the required JRE to use this software.
Such a jump would make sense when going to Kryo 6.0.0, not when doing a patch release.
To Reproduce
On my Linux system;
outputs
and
outputs
Java class version 61 is Java 17
Additional context
My renovate update build https://github.com/nielsbasjes/yauaa/actions/runs/11252889050/job/31286989023?pr=1598 fails with
[INFO] Restricted to JDK 8 yet com.esotericsoftware:kryo:jar:5.6.1:compile contains com/esotericsoftware/kryo/ClassResolver.class targeted to JDK 17
The text was updated successfully, but these errors were encountered: