Enforcing #checkstyle rules is a good way of preventing the propagation of badly-written code.

Source code is more difficult to read and more inviting to accidental mistake if some well-known bad practices are allowed.

Having a mix of coding styles for the same project can also lead to IDEs trying to amend each other (e.g. remove tabs, add spaces instead, or viceversa). That will probably leave traces on git, increasing review time.

Built-in Support for #JVM Code Quality Tools - The #Gradle distribution includes #plugins for:

#Checkstyle - https://docs.gradle.org/current/userguide/checkstyle_plugin.html
#CodeNarc - https://docs.gradle.org/current/userguide/codenarc_plugin.html
#PMD - https://docs.gradle.org/current/userguide/pmd_plugin.html
#JaCoCo - https://docs.gradle.org/current/userguide/jacoco_plugin.html

and many others.https://www.facebook.com/photo.php?fbid=634382428688716&set=a.528530279273932&type=3

I am amazed how #cs2pr, a small tool I built years ago, still attracts new users.

It helps you converting #checkstyle formatted output into #githubactions native annotation format.

enjoy!

https://github.com/staabm/annotate-pull-request-from-checkstyle

#Frustrated by things that make me sad: chasing dependency and !@#$@!$#ing #Java #CheckStyle linelength errors in an app suite (6 microservices) because I want to make a 3 line change

This is code that's been actively ignored for years, and yet (and yet!) is a significant revenue generator.

How the everlovin' fuck did I end up being the "expert" in it?

Answered: Does maven-checkstyle-plugin checks files only within the /src directory

https://stackoverflow.com/a/73148270/1549977

#maven #so #checkstyle