-
Notifications
You must be signed in to change notification settings - Fork 21
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
Java SE 17 required for Build Tools 2.39.0 #293
Comments
sugeeshC
added a commit
that referenced
this issue
Jun 20, 2024
…ls to Java 17. Signed-off-by: sugeesh chandraweera <[email protected]>
sugeeshC
added a commit
that referenced
this issue
Jun 20, 2024
…ls to Java 17. Signed-off-by: sugeesh chandraweera <[email protected]>
sugeeshC
added a commit
that referenced
this issue
Jun 27, 2024
…ls to Java 17. Signed-off-by: sugeesh chandraweera <[email protected]>
9 tasks
VenelinBakalov
added a commit
that referenced
this issue
Jul 1, 2024
…n-update [documentation] (#293) Required Java version updated to Java 17 in the documentation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
While not mentioned in the releases on GitHub, Java SE 17 is now required to run the build tools.
The setup-platform documentation still mentions your CI server needs Java 8.
Our current pipeline agent only has Java 8 and 11 active and now gives a
java.lang.UnsupportedClassVersionError
error with the text:We upgraded from 2.33.0 to 2.39.0 (were blocked from upgrading by #149) so maybe this changed in an earlier version.
If this is intentional, I'd suggest to update the documentation accordingly.
Steps to Reproduce
2.39.0
mvn clean package
Preconditions:
Have a system/pipeline agent with only Java 1.8 & 11 installed.
Expected behavior:
To build successfully without error.
Actual behavior:
We receive a
java.lang.UnsupportedClassVersionError
error.Reproduces how often:
100%
Component/s:
Not sure. Would think artifact-manager.
Affects Build/s:
2.39.0
Environment
Client (CI agent in this case)
Failure Logs
The text was updated successfully, but these errors were encountered: