You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Benson Margulies (JIRA)" <ji...@codehaus.org> on 2014/01/13 20:35:49 UTC

[jira] (MNG-4173) Remove automatic version resolution for POM plugins

    [ https://jira.codehaus.org/browse/MNG-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=338645#comment-338645 ] 

Benson Margulies commented on MNG-4173:
---------------------------------------

This will break a lot of builds. Arguably it should come in a box, like 4.0, that has many better reasons for breaking a lot of builds.

                
> Remove automatic version resolution for POM plugins
> ---------------------------------------------------
>
>                 Key: MNG-4173
>                 URL: https://jira.codehaus.org/browse/MNG-4173
>             Project: Maven 2 & 3
>          Issue Type: Task
>          Components: Plugins and Lifecycle
>    Affects Versions: 3.0-alpha-3
>            Reporter: Benjamin Bentmann
>             Fix For: 3.2
>
>
> Maven 3.x will no longer try to automatically find the version for plugins specified in the POM, i.e. the effective POM must declare a version for each plugin used for the sake of reproducible builds. Omitting the plugin version will raise in error.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira