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/08/06 08:30:27 UTC

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

    [ 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