You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2022/08/07 19:21:00 UTC
[jira] [Created] (MPLUGIN-416) Move reporting to a separate plugin
Michael Osipov created MPLUGIN-416:
--------------------------------------
Summary: Move reporting to a separate plugin
Key: MPLUGIN-416
URL: https://issues.apache.org/jira/browse/MPLUGIN-416
Project: Maven Plugin Tools
Issue Type: Task
Components: Plugin Plugin
Reporter: Michael Osipov
As noticed by me 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)