You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Guillaume Nodet (Jira)" <ji...@apache.org> on 2022/10/20 05:03:00 UTC
[jira] [Closed] (MPLUGIN-423) Extract plugin report into its own plugin
[ https://issues.apache.org/jira/browse/MPLUGIN-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet closed MPLUGIN-423.
-----------------------------------
Resolution: Fixed
> 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)