[
https://issues.apache.org/jira/browse/MDEPLOY-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965581#comment-17965581
]
Olivier Lamy commented on MDEPLOY-92:
-------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#146|https://github.com/apache/maven-deploy-plugin/issues/146].
> 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 (Moved to GitHub Issues)
> 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
(v8.20.10#820010)
