[jira] Updated: (MNG-3691) When a snapshot is deployed with uniqueVersion=false, it's SNAPSHOT dependencies must be forced to timestamp

["Brett Porter (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MNG-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MNG-3691:
------------------------------

    Fix Version/s: Reviewed Pending Version Assignment

maybe this needs to be a feature of the deploy plugin - the ability to deploy a "reproducible" snapshot where the versions get locked in, but it's not the default. It does make some sense.

Generally, you expect to retain the snapshot modifier so that you receive updates on the transitive dependencies.


> When a snapshot is deployed with uniqueVersion=false, it's SNAPSHOT dependencies must be forced to timestamp
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-3691
>                 URL: http://jira.codehaus.org/browse/MNG-3691
>             Project: Maven 2
>          Issue Type: Bug
>    Affects Versions: 2.0.9
>            Reporter: nicolas de loof
>             Fix For: Reviewed Pending Version Assignment
>
>
> use case :
> using the release plugin as a SNAPSHOT timestamped version to ensure reproductibility.
> When an incompatible  SNAPSHOT of the release-manager is deployed, the plugin doesn't work anymore : it updated it's SNAPSHOT dependencies.
> -> uniqueVersion=false was useless to ensure reproductibility.
> The isse is that the plugin POM has a SNAPSHOT dependency. As part of the deploy process, the SNAPSHOT version SHOULD be forced to current timestamped version to follow the uniqueVersion expectation.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira