[ https://issues.apache.org/jira/browse/MNG-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16315083#comment-16315083 ]
Hervé Boutemy edited comment on MNG-6054 at 1/7/18 7:25 AM: ------------------------------------------------------------ continued thinking: perhaps the behaviour on WARN when plugin version not locked should be changed a little bit on CLI invocation, just add an INFO message "using version XXX", since CLI is by definition not reproducible (and ideally, could even propose to choose from a list) on plugin bound to a build phase, the current WARN is the good behaviour: it's not reproducible when it should no idea if the CLI invocation feature would be easy or hard to implement... was (Author: hboutemy): continued thinking: perhaps the behaviour on WARN when plugin version not locked should be changed a little bit on CLI invocation, just add an INFO message "using version XXX", since CLI is by definition not reproducible (and ideally, could even propose to choose from a list) on plugin bound to a build phase, the current WARN is the good behaviour: it's not reproducible when it should > 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)