Skip to content

Drop JUnit 4, the vintage engine and Hamcrest from the plugin tests - #1427

Merged
slachiewicz merged 1 commit into
masterfrom
agent/junit4-out
Oct 10, 2026
Merged

slachiewicz merged 1 commit into
masterfrom
agent/junit4-out

Conversation

@slachiewicz

@slachiewicz slachiewicz commented Oct 10, 2026 •

Copy link
Copy Markdown
Member

Part of #1414, step 3.

After #1425 no test in versions-maven-plugin uses JUnit 4 or Hamcrest, so junit:junit, junit-vintage-engine and org.hamcrest:hamcrest leave its test dependencies. The last two deprecation warnings of the test sources go as well: PluginUpdatesReportTest reads the reporting plugins from the model, and TestWagonStub suppresses the warning on openConnection(), which the Wagon interface still declares.

The one deprecation warning left in the build is getDependencyArtifacts() in AbstractVersionsDependencyUpdaterMojo, which #1420 left for a change of its own. versions-common and versions-enforcer still use Hamcrest in their tests; #1414 tracks them.

Verified: mvn clean install -Dinvoker.skip โ†’ all modules pass, 297 tests in the plugin run on the JUnit 5 engine alone, 0 Checkstyle violations

@slachiewicz slachiewicz added the maintenance Cleanup, refactoring or other internal change label Oct 10, 2026
@slachiewicz
slachiewicz marked this pull request as ready for review October 10, 2026 19:45
Base automatically changed from agent/junit5-pom-updaters to master October 10, 2026 19:53
@slachiewicz
slachiewicz merged commit d2296f9 into master Oct 10, 2026
5 checks passed
@slachiewicz
slachiewicz deleted the agent/junit4-out branch October 10, 2026 19:59
@github-actions github-actions Bot added this to the 2.22.1 milestone Oct 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

maintenance Cleanup, refactoring or other internal change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant