[
https://issues.apache.org/jira/browse/MNG-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16315074#comment-16315074
]
Hervé Boutemy edited comment on MNG-6054 at 1/7/18 6:44 AM:
------------------------------------------------------------
I'm not sure this is a good idea: AFAIK, these plugins are plugins that are
usually invoked as direct goal from CLI (or at least some of these plugins)
Then providing default versions makes as much sense as providing default
versions for build lifecycle plugins (ie. it can be discussed, since users
should explicitely choose their version through pluginManagement)
was (Author: hboutemy):
I'm not sure this is a good idea: AFAIK, these plugins are plugins that are
usually invoked as direct goal from CLI
Then providing default versions makes s much sense as providing default
versions for build lifecycle plugins (ie. it can be discussed, since users
should explicitely choose their version through pluginManagement)
> Remove super POM plugin management section
> ------------------------------------------
>
> Key: MNG-6054
> URL: https://issues.apache.org/jira/browse/MNG-6054
> Project: Maven
> Issue Type: Task
> Affects Versions: 3.3.9
> Reporter: Christian Schulte
> Priority: Trivial
> Fix For: needing-scrub-3.4.0-fallout
>
>
> The super POM contains various plugins in the plugin management not part of
> any default lifecycle. These should be removed from the super POM.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
