-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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
Enforce fail on deprecated gradle usage #59598
Enforce fail on deprecated gradle usage #59598
Conversation
Pinging @elastic/es-core-infra (:Core/Infra/Build) |
This seems reasonable. We already do updates as PRs to ensure nothing explodes. Seems trivial to remove any newly introduced deprecations as part of that work. |
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.
👍
yeah, Tackling depreciations as part of the Gradle update is IMO the best way to deal with them. |
* Enforce fail on deprecated gradle usage (#59598) * Fix branch specific deprecated gradle api usages * Fix archiveVersion property usage
* Enforce fail on deprecated gradle usage (#59598) * Fix remaining gradle api deprecations
* Enforce fail on deprecated gradle usage (elastic#59598) * Fix remaining gradle api deprecations
This enforces the Gradle build to fail if a deprecated Gradle API was used in the build.
This guarantees us that we don't let deprecations sneak back into the build over time. A side effect of this though is, that when updating gradle versions, we need to tackle new deprecations as part of the update.