[
https://issues.apache.org/jira/browse/MPLUGIN-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617099#comment-17617099
]
ASF GitHub Bot commented on MPLUGIN-423:
----------------------------------------
kwin commented on PR #147:
URL:
https://github.com/apache/maven-plugin-tools/pull/147#issuecomment-1277712343
Please don't let me rewrite
https://github.com/apache/maven-plugin-tools/pull/139. This PR conflicts with
the other. Can we wait with this effort until #139 is merged?
> Extract plugin report into its own plugin
> -----------------------------------------
>
> Key: MPLUGIN-423
> URL: https://issues.apache.org/jira/browse/MPLUGIN-423
> Project: Maven Plugin Tools
> Issue Type: Task
> Reporter: Guillaume Nodet
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
