[
https://issues.apache.org/jira/browse/MDEPLOY-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MDEPLOY-92.
---------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> When a snapshot is deployed with uniqueVersion=false, its SNAPSHOT
> dependencies must be forced to timestamp
> -----------------------------------------------------------------------------------------------------------
>
> Key: MDEPLOY-92
> URL: https://issues.apache.org/jira/browse/MDEPLOY-92
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Reporter: nicolas de loof
> Priority: Major
> 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 was sent by Atlassian JIRA
(v7.6.3#76005)
