-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Support running Gradle on Java 20 #23488
Comments
Related: #23489 |
Due to lack of support for JDK 20 in Scala and Kotlin, we are pushing back support for running Gradle on Java 20 until 8.2. Gradle 8.1 will still have support for compiling, testing, etc. on JDK 20 as per #23489. |
Parked until Kotlin supports JDK 20. |
Kotlin 1.9.0-beta will have 20 |
Java 19 is already EOL, and Eclipse Temurin packages with Java 20 is readily available. However, Gradle doesn't support running on JDK 20 yet: gradle/gradle#23488. Hence, we need to keep the java19 alias for some more time.
Commented here: and here: expecting a fix! |
Java 19 is out of support, but Gradle current does not run on Java 20: gradle/gradle#23488 To avoid the complexity of running the build tool on a different JDK than the application, we temporarily remove code that depends on experimental Java 19 or Java 20 features. Revert once the build can run on Java 20.
Java 19 is out of support, but Gradle current does not run on Java 20: gradle/gradle#23488 To avoid the complexity of running the build tool on a different JDK than the application, we temporarily remove code that depends on experimental Java 19 or Java 20 features. Revert once the build can run on Java 20.
Introduce a new column that clarifies the different between using toolchains and running Gradle with a Java version. Issue #23488
…mpat table Introduce a new column that clarifies the different between using toolchains and running Gradle with a Java version. Issue #23488 Co-authored-by: Louis Jacomet <louis@gradle.com>
This contains no actual production changes, as with the Kotlin 1.9.0 upgrade this already works. These are simply test changes to verify that Gradle indeed runs on Java 20. Fixes #23488 Co-authored-by: Sterling Greene <sterling@gradle.com>
This contains no actual production changes, as with the Kotlin 1.9.0 upgrade this already works. These are simply test changes to verify that Gradle indeed runs on Java 20. Fixes #23488 Co-authored-by: Octavia Togami <otogami@gradle.com>
This contains no actual production changes, as with the Kotlin 1.9.0 upgrade this already works. These are simply test changes to verify that Gradle indeed runs on Java 20. Fixes #23488 Co-authored-by: Octavia Togami <otogami@gradle.com>
This contains no actual production changes, as with the Kotlin 1.9.0 upgrade this already works. These are simply test changes to verify that Gradle indeed runs on Java 20. Fixes #23488 Co-authored-by: Octavia Togami <otogami@gradle.com>
I have tried `8.3 RC 1: On Gradle
After upgrading to
|
That looks like a separate issue. Could you open a new issue with a minimal reproducer? |
Tried with Gradle 8.2.1, this repro-ed.
|
@atiq-cs look at the milestone of this issue it's 8.3 / 8.3 RC1, the fix is not yet released in 8.2.1 |
This contains no actual production changes, as with the Kotlin 1.9.0 upgrade this already works. These are simply test changes to verify that Gradle indeed runs on Java 20. Fixes #23488 Co-authored-by: Octavia Togami <otogami@gradle.com>
Closing as #25777 |
I could not find an issue for the problem reported by @igorwojda . I have verified I have the same problem with version 8.3-rc-4 and I opened a separate issue: #26125 I am adding this comment in case someone end up finding this issue, as I did, when looking for the problem reported by @igorwojda and experienced also by me |
No description provided.
The text was updated successfully, but these errors were encountered: