Explain why the legacy org.codehaus.doxia.sink.Sink stays Removing it breaks mvn site for report plugins that still declare generate(org.codehaus.doxia.sink.Sink, Locale): jacoco-maven-plugin 0.8.16 fails with 'A required class was missing ... org/codehaus/doxia/sink/Sink'. Do not delete it in a deprecation cleanup; the test keeps the type in place.
Turns the report plugins in a POM‘s <reporting> section into configured MavenReport instances. The Maven Site Plugin calls it during mvn site: it resolves each report plugin’s version, merges its configuration with build/pluginManagement, loads it in its own class realm and runs any forked lifecycle a report needs. Plugins that render reports themselves can call MavenReportExecutor the same way.
Requires Java 8 or later; built against the Maven 3.9 core API.
mvn verify
This also runs the integration tests under src/it, which drive report plugins through the executor, including forked lifecycles and report plugins built on different Doxia versions. Run one of them with mvn verify -Dinvoker.test=forked-lifecycle.
Send pull requests against master; discuss larger changes on the developer mailing list first. Spotless enforces the Maven code style during the build; run mvn spotless:apply before you push. Pull request titles become entries in the release notes.