You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2010/04/07 03:02:23 UTC
[jira] Closed: (MNG-3144) Snapshots not updated when using
uniqueVersion false
[ http://jira.codehaus.org/browse/MNG-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MNG-3144.
-----------------------------
Resolution: Incomplete
Fix Version/s: (was: 2.2.x (to be reviewed))
Assignee: Brett Porter
please let us know if you have answers to the questions
> Snapshots not updated when using uniqueVersion false
> ----------------------------------------------------
>
> Key: MNG-3144
> URL: http://jira.codehaus.org/browse/MNG-3144
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.7
> Reporter: Nicky Sandhu
> Assignee: Brett Porter
> Priority: Critical
>
> The particular scenario here is
> 1.) Deploy snapshot using uniqueVersion false in distribution management
> 2.) Verify repository has latest snapshot and metadata is updated in build number and timestamp
> 3. ) Goto a developer's machine (not the same as from which it was deployed) and do mvn -U or specify updates to be always in pom
> 4.) Local cache shows the maven metadata xml file is updated but the snapshot artifact (jar in this case) is not
--
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