-
Notifications
You must be signed in to change notification settings - Fork 28
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
Use Java target to 11 #653
Conversation
build.gradle
Outdated
@@ -37,6 +39,17 @@ subprojects { | |||
|
|||
kotlin.jvmToolchain(17) |
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 we can remove this now, too? No reason to use such an ancient JDK. Developers should always be using the latest one.
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.
Do you mean it should use the user JDK (and the JDK defined in the GitHub Actions workflows, which is 17) or that I should upgrade it to 21?
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.
The former, the "user"/global JDK. It'll fail if someone tries to use older than 11, but otherwise our actions should be using 23.
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.
Removed and version upgraded to 23 on the workflows 👍
I think the token to publish snapshots to Sonatype is broken. |
It is. |
SqlDelight is forced to use Java 17 for the Gradle plugin due sql-psi
core
dependency.This PR changes the target Java version to 11, but it still will use Java 17 in the toolchain as it has better build speed.
If you agree, upgrading the toolchain to Java 21 can be interesting as it should be faster.