Skip to content

Implement getOutputPath() and deprecate getOutputName() - #3469

Merged
slachiewicz merged 1 commit into
masterfrom
agent/doxia-2-adoption
Sep 10, 2026
Merged

slachiewicz merged 1 commit into
masterfrom
agent/doxia-2-adoption

Conversation

@slachiewicz

Copy link
Copy Markdown
Member

Adopts the report output method that Maven Reporting API 4.0.0 introduced, following the pattern in the report plugin guide and already used by maven-javadoc-plugin and maven-pmd-plugin: getOutputPath() carries the value, and getOutputName() stays as a deprecated delegate because the API still declares it abstract.

Both reports return the configurable outputName parameter as before, so the rendered paths do not change. AbstractSurefireReport now declares getOutputPath() abstract instead of getOutputName().

The surefire-3.5.x line is not touched: it is the Doxia 1 line for this plugin and Maven Reporting API 3.x has no getOutputPath().

Verified: mvn test -pl maven-surefire-report-plugin β†’ 14 tests, 0 failures.

This change was created with AI assistance.

Maven Reporting API 4.0.0 keeps getOutputName() abstract, so it cannot simply
be renamed: it stays, deprecated, delegating to the new method. Do not collapse
the pair until the API drops getOutputName().
@slachiewicz
slachiewicz marked this pull request as ready for review September 10, 2026 10:39
@slachiewicz
slachiewicz merged commit 82b187a into master Sep 10, 2026
19 checks passed
@slachiewicz
slachiewicz deleted the agent/doxia-2-adoption branch September 10, 2026 10:39
@github-actions github-actions Bot added this to the 3.6.1 milestone Sep 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant