Teamscale VS Checkstyle

> - The project already exists, and now you need to refactor out all the compile-time errors in order to move forward (time-consuming). Use a static analysis tool with proper, non-brittle tracking of new vs old findings (including proper move and copy file tracking) and forbid new findings, e.g. By preventing offending code from being merged to master with tools like Gitlab, Bitbucket, what have you. Works very... - Source: Hacker News / over 2 years ago

PMD and Checkstyle are static analysis tools that check your code on each project build. Gradle allows to apply them easily. - Source: dev.to / about 1 year ago

AFAIK, you can't use it with nvim-jdtls, but here you shave a list of checkstyle plugins and there are a Gradle and a Maven one that your could use. Source: over 1 year ago

The generated classes should be put into .gitignore. Otherwise, if you have Checkstyle, PMD, or SonarQube in your project, then generated classes can violate some rules. Besides, if you don't put them into .gitignore, then each pull request might become huge due to the fact that even a slightest fix can lead to lots of changes in the generated classes. - Source: dev.to / over 1 year ago

Speaking of code style there aren't many differences. You can try Checkstyle plugin. It automatically fails a build that violates any of the stated requirements. For example, the code might have an unused import. Besides you can look at cloud services that run the code analysis and shows the result as a bunch of charts (SonarCloud can also do that). - Source: dev.to / over 2 years ago

Java developers use powerful IDEs that lint code in realtime. Powerful as they are, they are not enough. Quality checks must also be part of the CI pipeline. We can use checkstyle to add a linting job. - Source: dev.to / about 3 years ago