[
https://issues.apache.org/jira/browse/MPLUGIN-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570508#comment-17570508
]
ASF GitHub Bot commented on MPLUGIN-388:
----------------------------------------
slawekjaranowski commented on PR #66:
URL:
https://github.com/apache/maven-plugin-tools/pull/66#issuecomment-1193349873
> I would consider to move this part to a `maven-plugin-reporting-plugin`.
Similar to Surefire.
Idea is good, but it will be breaking change, we will have new artifact for
reporting section.
> Make reporting optional dependency
> ----------------------------------
>
> Key: MPLUGIN-388
> URL: https://issues.apache.org/jira/browse/MPLUGIN-388
> Project: Maven Plugin Tools
> Issue Type: Task
> Components: Plugin Plugin
> Reporter: Tamás Cservenák
> Priority: Major
>
> Current m-p-p is far from being "lightweight", mostly due
> maven-reporting-impl being pulled in (that pulls in doxia, http-client and
> almost whole universe), and all this due one single mojo, the {{report}} mojo
> (org.apache.maven.plugin.plugin.PluginReport), and all these dependencies are
> needed ONLY when mojo directly invoked (ie. {{{}mvn m-p-p:report{}}}), as
> when used as part of site, all these are provided by site plugin.
> Make this dependency optional. This implies, that users of this release using
> report mojo "standalone" MUST ADD maven-reporting-impl:3.0.0 as dependency to
> m-p-p plugin as plugin dependency.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
