-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Fix checkstyle version drift and API change #88283
Fix checkstyle version drift and API change #88283
Conversation
Pinging @elastic/es-delivery (Team:Delivery) |
Why didn’t the build fail with this conflict? Can we fail going forward in this situation so that we don’t have this jarhell again? |
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.
lgtm
...ions/src/main/java/org/elasticsearch/gradle/internal/checkstyle/MissingJavadocTypeCheck.java
Outdated
Show resolved
Hide resolved
We don't apply the custom Checkstyle in the CLI build, only in the IDE. We would have caught this if we didn't duplicate the Checkstyle version declaration. @breskeby said he'd look into consolidating them. |
…nal/checkstyle/MissingJavadocTypeCheck.java Co-authored-by: Rene Groeschke <[email protected]>
Fix checkstyle version drift and API change.
Fix checkstyle version drift and API change.
We only rely on the checkstyle version in the buildLibs.toml gradle version catalogue with this change. Also added some hints for gradle best practices. This is an aftermath of #88283
We only rely on the checkstyle version in the buildLibs.toml gradle version catalogue with this change. Also added some hints for gradle best practices. This is an aftermath of elastic#88283
It turns out we have the Checkstyle version in 2 places:
build-tools-internal/version.properties
gradle/build.versions.toml
This concealed that there was an API change between 10.1 and 10.3, and we needed to update one of our custom checks.