You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/10/11 16:11:00 UTC
[jira] [Commented] (MPLUGIN-388) Make reporting optional dependency
[ https://issues.apache.org/jira/browse/MPLUGIN-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17615937#comment-17615937 ]
ASF GitHub Bot commented on MPLUGIN-388:
----------------------------------------
gnodet commented on PR #66:
URL: https://github.com/apache/maven-plugin-tools/pull/66#issuecomment-1274942661
@slachiewicz @slawekjaranowski @cstamas so what's the status of this PR ? I've merged master, but should that be integrated into the upcoming 3.7.0 release or delayed ?
> 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: Tamas Cservenak
> 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)