-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Upgrade workflow to run unit tests in Java 17 - the latest LTS #3139
Comments
Sure thing! Will be interesting to see if it works. (I expect it will.) |
But probably we will replace 16 with 17 (instead of just adding 17) when it gets out. For efficiency, we don't want to test on every Java version. Probably only LTS versions. |
So can I make the change?. I understand that it's much efficient to stick with the LTS version. Still, In my opinion, it would be good to have at least one or two non-LTS versions for unit tests to understand compatibility with different JDK versions. Thoughts? |
Sure, go ahead. I was just mentioning that when 17 comes out, we will probably drop 16. |
Modified the title to "Upgrade workflow to java 17 (the latest LTS) " |
This seems urgent due to sonarcloud warning
Prerequisite is update to a Gradle version that supports Java 17 (cf https://docs.gradle.org/current/userguide/compatibility.html#java): #4139 |
Java 16 is GA. Let me know if we can upgrade the workflow yml file to include JDK 16 also as part of running the unit test.
The text was updated successfully, but these errors were encountered: