Skip to content

chore: Fix pmd test setup - #6728

Merged
adangel merged 5 commits into
pmd:mainfrom
adangel:chore/fix-pmd-test-setup
Jun 11, 2026
Merged

adangel merged 5 commits into
pmd:mainfrom
adangel:chore/fix-pmd-test-setup

Conversation

@adangel

@adangel adangel commented May 28, 2026

Copy link
Copy Markdown
Member

Describe the PR

It turns out, that JUnit5TestShouldBePackagePrivate didn't trigger after all, although it has been fixed with #6680.

The reason was, that when using includeTests=false, the wrong classpath was used by m-pmd-p and e.g. JUnit was missing - and the rule didn't detect any test classes.

Related issues

  • Fix #

Ready?

  • Added unit tests for fixed bug/feature
  • Passing all unit tests
  • Complete build ./mvnw clean verify passes (checked automatically by github actions)
  • Added (in-code) documentation (if needed)

@adangel adangel added this to the 7.26.0 milestone May 28, 2026
@adangel adangel added the in:pmd-internals Affects PMD's internals label May 28, 2026
@UncleOwen

Copy link
Copy Markdown
Member

Thanks for catching this. The other changes look fine.

@pmd-actions-helper

pmd-actions-helper Bot commented May 28, 2026 •

Copy link
Copy Markdown
Contributor

Documentation Preview

No relevant source code has been changed, pmdtester skipped.

(comment created at 2026-06-11 08:35:14+00:00 for 8b7c112)

@adangel
adangel force-pushed the chore/fix-pmd-test-setup branch from 535d503 to 0c30e92 Compare June 5, 2026 09:10
@adangel
adangel requested a review from UncleOwen June 5, 2026 09:13
@adangel
adangel merged commit fe99e85 into pmd:main Jun 11, 2026
12 checks passed
@adangel
adangel deleted the chore/fix-pmd-test-setup branch June 11, 2026 08:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

in:pmd-internals Affects PMD's internals

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants