You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Zoltan Farkas (JIRA)" <ji...@apache.org> on 2016/07/05 20:54:11 UTC
[jira] [Comment Edited] (MNG-4173) Remove automatic version
resolution for POM plugins
[ https://issues.apache.org/jira/browse/MNG-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363217#comment-15363217 ]
Zoltan Farkas edited comment on MNG-4173 at 7/5/16 8:53 PM:
------------------------------------------------------------
Would it be possible to have this available as a option before 4.0? The option default would be backwards compatible... so that it would have less of an impact.
I find it very important to have reproducible builds...
see: http://stackoverflow.com/questions/25983852/maven-javadoc-plugin-breaks-mvn-releaseperform for detail...
was (Author: zolyfarkas):
Would it be possible to have this available as a option before 4.0? The option default would be backwards compatible... so that it would have less of an impact.
I find it very important to have reproducible builds...
> Remove automatic version resolution for POM plugins
> ---------------------------------------------------
>
> Key: MNG-4173
> URL: https://issues.apache.org/jira/browse/MNG-4173
> Project: Maven
> Issue Type: Task
> Components: Plugins and Lifecycle
> Affects Versions: 3.0-alpha-3
> Reporter: Benjamin Bentmann
> Fix For: Issues to be reviewed for 4.x
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)