Apache Maven Reporting Executor

Clone this repo:
  1. aa4c572 Explain why the legacy org.codehaus.doxia.sink.Sink stays by Sylwester Lachiewicz · 5 days ago master
  2. ed26848 Simplify setReportPlugins conversion by Sylwester Lachiewicz · 4 days ago
  3. 69863e1 Refresh the site index and README for 2.1.0 by Sylwester Lachiewicz · 5 days ago
  4. 5f9ae57 Use JUnit 5 assertions and Mockito best practices in tests by Sylwester Lachiewicz · 6 days ago
  5. 97d7cb8 Replace remaining StringUtils and Commons calls with the JDK by Sylwester Lachiewicz · 6 days ago

Apache Maven Reporting Executor

Apache License, Version 2.0, January 2004 Maven Central Reproducible Builds Verify

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.

Build

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.

Contributing

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.