-
Notifications
You must be signed in to change notification settings - Fork 10
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
Upgrade to Gradle 7 #99
Comments
I have tried to upgrade the plugin to use Gradle 7 in the past but I wasn’t able to do so due to some challenges around Gradle using an older version of Apache Groovy vs the plugin on higher (or latest) version of it. I think this is due to some changes around how a Gradle 7 plugin uses Groovy which results in the tight coupling between Groovy and Gradle. I don’t recall the specifics now and would need to spend more time to share the exact details. Moreover, I am waiting for the Gradle 7 version which uses Groovy 3.0.11. |
Gradle 7.6 already published with Groovy 3.0.13. The main thing is to solve a lot of STC in Groovy 3.0.10+, GORM should be fixed with some STC errors first. > gradle -v
------------------------------------------------------------
Gradle 7.6
------------------------------------------------------------
Build time: 2022-11-25 13:35:10 UTC
Revision: daece9dbc5b79370cc8e4fd6fe4b2cd400e150a8
Kotlin: 1.7.10
Groovy: 3.0.13
Ant: Apache Ant(TM) version 1.10.11 compiled on July 10 2021
JVM: 1.8.0_345 (Azul Systems, Inc. 25.345-b01) |
@puneetbehl https://github.com/bmuschko/gradle-nexus-plugin
|
@rainboyan I think we can move away from gradle-nexus-plugin and use alternatives for pushing the artefacts to Maven Central. I believe we are already doing this on other repositories. Thanks! |
Gradle 7.0 was released for a while. Gradle support JDK 16 and use Groovy 3 in Groovy DSL build scripts.
And here‘s a Gradle upgrade guide about upgrading build and plugins to be compatible with Groovy 3.
Upgrade to 7.0 will also remove some warnings from Gradle:
The text was updated successfully, but these errors were encountered: