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

["Robert Scholte (JIRA)" <ji...@codehaus.org>]

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

Robert Scholte commented on MDEPLOY-92:
---------------------------------------

I'm having trouble with the idea to use a timestamped snapshot to ensure reproducibility, since snapshots are always the first targets for cleanup. Instead I'd strongly prefer revisions to be included when generating the artifact if there's an SCM involved.
                
> 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 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira