slachiewicz opened a new pull request, #1643:
URL: https://github.com/apache/maven-site/pull/1643
The template on this page built against Doxia 1.10, `maven-reporting-impl`
3.0.0 and
`maven-reporting-api` 3.0, so anyone following it today writes a new plugin
against the stack
that was superseded by Doxia 2.0.0.
Beyond the version numbers, three things the bump alone does not give you:
- `MavenProject` no longer arrives transitively — `maven-reporting-impl`
4.0.0 declares `maven-core`
as `provided`, so the sample needs its own `provided` `maven-core` or it
does not compile.
- `getOutputName()` is deprecated in 4.0.0 but still abstract on
`MavenReport`, so it cannot simply
be replaced. The sample now implements `getOutputPath()` and delegates the
deprecated method to
it, matching what `maven-javadoc-plugin` does.
- `AbstractMavenReport` already declares `protected MavenProject project`,
so the sample's own
`@Parameter`-annotated field was shadowing it; removed.
The unused `maven-shared-utils` dependency is dropped in the same pass —
nothing in the sample
imports it.
Verified: built the page's two samples as a real plugin, `mvn install`, then
ran `mvn site` on a
consumer project declaring it under `<reporting>` —
`target/site/simple-report.html` is generated
and listed in `project-reports.html`, and the compile is free of deprecation
warnings. The blocks in
the page are byte-identical to what was built.
*This change was created with AI assistance.*
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
