You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "nicolas de loof (JIRA)" <ji...@codehaus.org> on 2008/07/31 15:05:26 UTC
[jira] Created: (MNG-3691) When a snapshot is deployed with
uniqueVersion=false, it's SNAPSHOT dependencies must be forced to timestamp
When a snapshot is deployed with uniqueVersion=false, it's SNAPSHOT dependencies must be forced to timestamp
------------------------------------------------------------------------------------------------------------
Key: MNG-3691
URL: http://jira.codehaus.org/browse/MNG-3691
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.9
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
[jira] Commented: (MNG-3691) When a snapshot is deployed with
uniqueVersion=false, it's SNAPSHOT dependencies must be forced to timestamp
Posted by "nicolas de loof (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144247#action_144247 ]
nicolas de loof commented on MNG-3691:
--------------------------------------
I understand well the snapshot usage with automatic updates when a new one is deployed. I dont undeerstand the use case of uniqueVersion=false if this is not to allow sort of "timestamp" version that ensure some reproductibility. To use such a timestamp, my POM needs to force all plugin SNAPSHOT dependencies versions.
Maybe the enforcer and release plugins should also check for this when they accept a timestamp for a plugin or dependency
> When a snapshot is deployed with uniqueVersion=false, it's SNAPSHOT dependencies must be forced to timestamp
> ------------------------------------------------------------------------------------------------------------
>
> Key: MNG-3691
> URL: http://jira.codehaus.org/browse/MNG-3691
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.9
> Reporter: nicolas de loof
> Fix For: Reviewed Pending Version Assignment
>
>
> 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
[jira] Moved: (MDEPLOY-92) When a snapshot is deployed with
uniqueVersion=false, it's SNAPSHOT dependencies must be forced to timestamp
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MDEPLOY-92) When a snapshot is deployed with
uniqueVersion=false, it's SNAPSHOT dependencies must be forced to timestamp
Posted by "Stephen Connolly (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MNG-3691) When a snapshot is deployed with
uniqueVersion=false, it's SNAPSHOT dependencies must be forced to timestamp
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3691:
------------------------------
Fix Version/s: Reviewed Pending Version Assignment
maybe this needs to be a feature of the deploy plugin - the ability to deploy a "reproducible" snapshot where the versions get locked in, but it's not the default. It does make some sense.
Generally, you expect to retain the snapshot modifier so that you receive updates on the transitive dependencies.
> When a snapshot is deployed with uniqueVersion=false, it's SNAPSHOT dependencies must be forced to timestamp
> ------------------------------------------------------------------------------------------------------------
>
> Key: MNG-3691
> URL: http://jira.codehaus.org/browse/MNG-3691
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.9
> Reporter: nicolas de loof
> Fix For: Reviewed Pending Version Assignment
>
>
> 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