Modernize Java quality checks and formatting ownership#3328
Merged
Conversation
pratushnyi
approved these changes
May 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
This PR updates the repository’s Java quality setup so formatting and static checks have clearer responsibilities. Formatting is now owned by Spotless with Eclipse JDT, while Checkstyle, PMD, and SpotBugs focus on distinct categories of source structure, maintainability, and bytecode-level issues.
The change reduces duplicate or noisy checks, removes obsolete suppressions, and applies the new formatter across the codebase. For users and contributors, this should make quality feedback easier to understand: formatting problems are fixed consistently by one tool, while deeper findings are reported by the tools best suited for them.
SpotBugs analysis was also tightened by excluding generated sources and improving its auxiliary classpath, so its results should be less noisy and more reliable. No runtime behavior is intended to change.
Checklist