-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[regression] Publish nightly releases and releases using Java 8 #19722
Conversation
@@ -723,6 +723,8 @@ jobs: | |||
SONATYPE_USER: ${{ secrets.SONATYPE_USER_ORGSCALALANG }} | |||
|
|||
steps: | |||
- name: Set JDK 8 as default |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we don't explicitly set the version, CI will use Java 21
- name: Set JDK 17 as default | ||
run: echo "/usr/lib/jvm/java-17-openjdk-amd64/bin" >> $GITHUB_PATH | ||
- name: Set JDK 8 as default | ||
run: echo "/usr/lib/jvm/java-8-openjdk-amd64/bin" >> $GITHUB_PATH |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just for making the build future-proof, we should add explicit -source/-release/-target flags to JDK to always emit JDK 8 bytecode and use only JDK API available in that version.
Same issue might be also present in normal releases
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this would have to be set in SBT, not in the CI configuration. The best we can do from the CI point of view is switch the default Java version.
CI failure is similar to #18344. Restarting the CI might fix it (See #19535) |
Close #19721
[test_java8]