[
https://issues.apache.org/jira/browse/MPLUGIN-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17620742#comment-17620742
]
Hudson commented on MPLUGIN-423:
--------------------------------
Build failed in Jenkins: Maven » Maven TLP » maven-plugin-tools » master #60
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-plugin-tools/job/master/60/
> 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
> Assignee: Guillaume Nodet
> Priority: Major
> Fix For: 3.7.0
>
>
> 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)
