fix: satisfy PMD 7.27.0 across the reactor - #1530
Merged
Merged
Conversation
This was referenced Sep 8, 2026
Bumps `pmd.version` from 7.26.0 to 7.27.0. Updates `net.sourceforge.pmd:pmd-core` from 7.26.0 to 7.27.0 - [Release notes](https://github.com/pmd/pmd/releases) - [Commits](pmd/pmd@pmd_releases/7.26.0...pmd_releases/7.27.0) Updates `net.sourceforge.pmd:pmd-java` from 7.26.0 to 7.27.0 - [Release notes](https://github.com/pmd/pmd/releases) - [Commits](pmd/pmd@pmd_releases/7.26.0...pmd_releases/7.27.0) --- updated-dependencies: - dependency-name: net.sourceforge.pmd:pmd-core dependency-version: 7.27.0 dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: net.sourceforge.pmd:pmd-java dependency-version: 7.27.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> (cherry picked from commit ab016b0) (cherry picked from commit 188fcd5) (cherry picked from commit bf45170) (cherry picked from commit 4d4ef4f) (cherry picked from commit 9b6c414) (cherry picked from commit 73532f0)
joaodinissf
requested review from
KrisLimbo and
markdomeng
and removed request for
rubenporras
September 8, 2026 09:38
joaodinissf
force-pushed
the
fix/pmd-7.27-compat
branch
from
September 8, 2026 09:42
296d03b to
e143f56
Compare
Eulan2025
approved these changes
Sep 10, 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
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.
Summary
Upgrade PMD from 7.26.0 to 7.27.0 and address only the reproduced warnings, without optional refactoring. The version bump from Dependabot #1514 is included; close #1514 after this PR merges.
Scope
The unfixed PR base with PMD 7.27 produces 24 violations across 19 Java files: 4 InstantiableUtilityClass, 13 ProtectedMemberInFinalClass, 4 ReturnEmptyCollectionRatherThanNull, and 3 UnusedReturnValue. Report generation across all modules was necessary because the normal fail-at-end check skips downstream modules after the initial failures.
@returntag because local Checkstyle rejects it; unrelated comment cleanup is excluded.Optional simplifications and their behavioral tests are being submitted in a separate dependent draft PR. They are not prerequisites for merging this PMD update.
Validation
The warning audit used Java 21 and CI's exact Maven PMD/CPD goals on macOS. The original five blocking CI findings reproduced, and report-only execution exposed all 24 findings across 62 PMD reports; 62 CPD reports contained no duplicates.
Full local verification and quality checks passed on head
296d03baa: Maven verify, Checkstyle, PMD, CPD, and SpotBugs. The aggregate suite reported 354 tests, 0 failures, 0 errors, and 2 skipped. This was Java 21 on macOS, using the repository's macOS UI profile. Fresh remote checks are still required on this head; previous-head CI is not evidence for this revision.Keep draft with no reviewer requests pending validation and review.
Re-homed from #1515: the branch moved from the fork to
upstreamso the dependent PR can be linked as a native stack (GitHub rejects fork PRs in stacks). Content is identical — same head commit296d03ba.🤖 Generated with Claude Code