-
Notifications
You must be signed in to change notification settings - Fork 360
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
Require JDK 17 for building #536
Comments
+1 here. |
… a few plugins (fixes apache#536)
This might require changing the CI builds. We still should test on Java 8. Might require maven toolchains. Otherwise fine by me. |
I'm working on CI. I've set up a |
Then we're not really requiring Java 11 for building. So still no multi-release. I would require 11 (or even 17) for compiling/building always; just run the tests on different JVMs (8, 11, 17). That's why I mentioned toolchains. I think there is a way to tell surefire to use a specific toolchain. |
… a few plugins (fixes apache#536)
The #537 PR now does that. I've bumped to JDK 21, but we can go down if we want. |
You can use JDK 21 in CI, but I would not require it as minimum for building. Still looks more complicated that needed. I'm not at my development machine, so I cannot verify myself that this would work, but it seems to me the following patch would be a minimal change to build with Java 11 and test on JDK 8, 11, 17:
This should use toolchains only in CI, so building locally doesn't require people to define toolchains manually. Adapting to build with Java 21 and running tests on 8,11,17,21 would be simple. |
Description
Bump the minimal JDK version required for building to java 17.
Motivation
This will streamline the build, allow upgrading to more recent plugins.
The minimal JDK requirement for runtime will be unchanged at JDK 8.
The text was updated successfully, but these errors were encountered: