[ 
https://issues.apache.org/jira/browse/MNG-5968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16315068#comment-16315068
 ] 

ASF GitHub Bot commented on MNG-5968:
-------------------------------------

Github user hboutemy commented on the issue:

    https://github.com/apache/maven/pull/151
  
    I'm not a fan of default plugins updates in core:
    - depending on default versions is a bad practice, we expect users to 
explicitely choose their version through pluginManagement (and we display a big 
WARNING in case they don't do it)
    - it changes behaviour when switching from one mvn version to the other
    
    then IMHO changing default plugins version should really be driven by key 
issues that we really want to avoid for untrained people (who don't know the 
requirement to define their choice): for example MNG-5992 would such an 
exception (default security is more important than helping people know that 
they need to choose their plugins versions by letting old plugins versions by 
default)


> plugin version updates in Maven core build
> ------------------------------------------
>
>                 Key: MNG-5968
>                 URL: https://issues.apache.org/jira/browse/MNG-5968
>             Project: Maven
>          Issue Type: Improvement
>    Affects Versions: 3.3.9
>            Reporter: Christian Schulte
>            Assignee: Michael Osipov
>            Priority: Minor
>             Fix For: 3.5.0-alpha-1, 3.5.0
>
>
> upgrade some plugins in Maven core build (pom.xml), just because newest are 
> expected to be better (no known bug):
> ||groupId||artifactId||previous version||target version||
> |{{org.codehaus.mojo}}|{{buildnumber-maven-plugincol}}|1.2|1.4|
> |{{org.codehaus.mojo}}|{{animal-sniffer-maven-plugin}}|1.14|1.15|
> |{{org.apache.maven.plugins}}|{{maven-doap-plugin}}|1.1|1.2|



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to