-
Notifications
You must be signed in to change notification settings - Fork 270
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
Gradle 8.2 compatibility #1413
Comments
1 task
11 tasks
I had a quick look, it doesn't seem it needs a breaking change. In my simple project there are only a few usages, all centralized in the same method There's 5 usages of `org.gradle.api.plugins.JavaPluginConvention`
There's 5 usages of `Project.getConvention()`
There's a 4 usages of `org.gradle.api.plugins.Convention`
Raised #1416 to fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Gradle 8.2 deprecated conventions with nagging. They were deprecated for a long time, but without nagging.
https://docs.gradle.org/8.2-rc-2/userguide/upgrading_version_8.html#deprecated_access_to_conventions
Describe the solution you'd like
Migrate away from using conventions to extensions, so builds can pass nicely even with
org.gradle.warning.mode=fail
. At Gradle 9.0 this will become an error, so sooner or later the migration has to be done. Better do it sooner :)Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
(this is just one example, you can see all usages at https://github.com/TWiStErRob/net.twisterrob.chroma/actions/runs/5355711906/jobs/9714328563?pr=13)
The text was updated successfully, but these errors were encountered: