You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/12/18 15:00:19 UTC
[jira] Moved: (MDEPLOY-92) When a snapshot is deployed with
uniqueVersion=false, it's SNAPSHOT dependencies must be forced to timestamp
[ http://jira.codehaus.org/browse/MDEPLOY-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved MNG-3691 to MDEPLOY-92:
------------------------------------------
Affects Version/s: (was: 2.0.9)
Fix Version/s: (was: Reviewed Pending Version Assignment)
Key: MDEPLOY-92 (was: MNG-3691)
Project: Maven 2.x Deploy Plugin (was: Maven 2)
> When a snapshot is deployed with uniqueVersion=false, it's SNAPSHOT dependencies must be forced to timestamp
> ------------------------------------------------------------------------------------------------------------
>
> Key: MDEPLOY-92
> URL: http://jira.codehaus.org/browse/MDEPLOY-92
> Project: Maven 2.x Deploy Plugin
> Issue Type: Bug
> Reporter: nicolas de loof
>
> 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