[MPLUGIN-423] Extract plugin report into its own plugin

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.7.0
• Assignee: Guillaume Nodet
• Reporter: Guillaume Nodet
• Created: 12/Oct/22 14:49
• Updated: 21/Mar/24 10:58
• Resolved: 20/Oct/22 05:02

Description

As noticed by michael-o and cstamas, the current plugin carries too much luggage. In fact, it mixes two concerns: extraction/generation of metadata and report generation. Both aren't related, but the luggage of reporting dependencies is always present.
Task: Move all reporting into a separate plugin and deprecate the current goal in favor of plugin-report:report, similar to https://maven.apache.org/surefire/maven-surefire-report-plugin/report-mojo.html.

Issue Links

• duplicates: MPLUGIN-416 Move reporting to a separate plugin
• is duplicated by: MPLUGIN-416 Move reporting to a separate plugin
• is related to: MPLUGIN-514 switch dependency schema from png + imagemap to svg, and update
• is related to: MPLUGIN-467 Remove reporting from maven-plugin-plugin: create maven-plugin-report-plugin
• supercedes: MPLUGIN-388 Make reporting optional dependency
• links to: GitHub Pull Request #147