Java 21: The Nice, the Meh, and the Momentous

Re:Java 21: The Nice, the Meh, and the Momentous by NovaX on Friday September 22, 2023 @09:30PM (#37619849)

Kotlin, not Groovy, has been the culprit for slower Gradle support. I believe there was some split module pain in Groovy wrt Java 9, but it has been very smooth since then. The Kotlin compiler on the other hand is not very forgiving.

This is a moot point because your the build execution and the project compile/run can be on different JDKs. It is a tiny amount of configuration to decouple them, e.g. to use an EA build.

[ Parent | on HN ]

Re:Java 21: The Nice, the Meh, and the Momentous by krzyk on Saturday September 23, 2023 @07:05AM (#37622144)

Yeah, you are right that decoupling build tool JDK and compile JDK is the way to go.

But Groovy does indeed not work, or has support very late for releases between 8, 11, 17 and 21 - so for anyone that wants to stay current (and not wait 3 or 2 years), using groovy in your code will be a pain - that might be also possible for other JVM languages, but I don't know, haven't used them.

[ Parent | on HN ]

Re:Java 21: The Nice, the Meh, and the Momentous by NovaX on Saturday September 23, 2023 @12:28PM (#37624725)

Oh interesting. Typically the gradle release notes, like 8.4-rc-1, will have comments that imply that Groovy build scripts compile but Kotlin ones lag.

"Gradle now supports using Java 21 for compiling, testing, and starting other Java programs. This can be accomplished using toolchains. Currently, you cannot run Gradle on Java 21 because Kotlin lacks support for JDK 21. However, support for running Gradle with Java 21 is expected in future versions."

https://docs.gradle.org/8.4-rc-1/release-notes.html#support-...

[ Parent | on HN ]