-
Notifications
You must be signed in to change notification settings - Fork 134
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
checkstyle 8.36 -> 8.37 (and keep it up to date using excavator) #1546
Conversation
Generate changelog in
|
|
||
if (gradle.startParameter.isWriteDependencyLocks()) { | ||
gradle.startParameter.taskNames += 'writeCheckstyleVersion' | ||
} |
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.
an alternative approach here is to generate the resource just-in-time as a dependency of the ./gradlew idea task... no super strong opinions, i just kinda like that this one is reasonably bulletproof
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.
Also no strong opinion but I like doing this as part of "--write-locks" as people already expect their version numbers to change through this run.
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, in general I hate it when i open intellij and something crucial is missing because it failed to generate somehow. this seemed more idiot dan-proof
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.
nice!
Released 3.51.0 |
Before this PR
@fawind is putting in a bunch of work to allow people to use some more 'cutting edge' java syntax (e.g. records). Checkstyle seems to be landing a lot of bugfixes related to these new features at the moment, e.g.
https://checkstyle.sourceforge.io/releasenotes.html
Currently, as the checkstyle version is read out of a private static field, it has to be manually updated. This means we're probably going to miss bugfixes until someone complains about them.
After this PR
==COMMIT_MSG==
checkstyle 8.36 -> 8.37, to benefit from some bugfixes to do with new java language features (e.g. records)
==COMMIT_MSG==
Possible downsides?