[
https://issues.apache.org/jira/browse/MNG-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16315076#comment-16315076
]
Hervé Boutemy commented on MNG-6054:
------------------------------------
after linking to a few Jira issues that help remember how we get there
(MNG-3395, MNG-4453)
I also verified the list of non-lifecycle bound plugins defined in Maven parent
POM:
- maven-antrun-plugin
- maven-assembly-plugin
- maven-dependency-plugin
- maven-release-plugin
AFAIK, antrun and assembly don't make sense as direct goal invocation: removing
default version in Super POM could be better than providing one version (and
discussing if we should update it from Maven core version to Maven core version
or not)
For dependency and release, direct goal invocation make sense: re-thinking at
it, I'm not sure this fact changes the evaluation on "should we provide a
default version"
analyzing: providing a default version in Super POM permits to avoid a WARN
message when user did not configure his choice of plugin version (since the
Super POM de-facto provided a plugin version). It gives a better user
experience for newbies or lazy situations, but it does not help people make
their choice: relying on a default version defined by Maven core is risky for
stability over time.
On these 4 plugins, I would perhaps only keep dependency since it's often used
as CLI, and the risk on stability seems quite low.
But for the 3 others, ensuring stability seems a higher priority: removing them
would be finally an improvement, even if it starts by hurting people used to
rely on the long habit of getting a default version.
And for sure, while at it, removing the 4th one... I'm torn.
But really, permitting "mvn dependency:analyze" without getting a WARN (given
it's not so often that you use dependency plugin in the build) is a useful UX
> 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.
> see http://maven.apache.org/ref/3.5.2/maven-model-builder/super-pom.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
