[
https://jira.codehaus.org/browse/MDEPLOY-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276650#comment-276650
]
Stephen Connolly commented on MDEPLOY-92:
-----------------------------------------
See http://mojo.codehaus.org/versions-maven-plugin/lock-snapshots-mojo.html for
a goal to use to pin the -SNAPSHOTs for you.
The reality is that you may have some artifacts being deployed to a different
repo with a different uniqueVersion setting.
Also Nicolas is this title incorrect, I assume you mean uniqueVersion=true as
when uniqueVersion=false you don't get the timestamp deployment.
> When a snapshot is deployed with uniqueVersion=false, it's SNAPSHOT
> dependencies must be forced to timestamp
> ------------------------------------------------------------------------------------------------------------
>
> Key: MDEPLOY-92
> URL: https://jira.codehaus.org/browse/MDEPLOY-92
> Project: Maven 2.x Deploy Plugin
> Issue Type: Bug
> Reporter: nicolas de loof
> Labels: scrub-review-started
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
