[
http://jira.codehaus.org/browse/MNG-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249860#action_249860
]
Brett Porter commented on MNG-4955:
-----------------------------------
Good timing with this report... I was about to file myself. I've noticed it in
differing behaviour between building in the reactor (where just-built snapshots
are used) and subsequently building a single module.
> [regression] Outdated remote snapshots are preferred over locally installed
> snapshots
> -------------------------------------------------------------------------------------
>
> Key: MNG-4955
> URL: http://jira.codehaus.org/browse/MNG-4955
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies
> Affects Versions: 3.0.1
> Reporter: Benjamin Bentmann
>
> When using the new metadata format, remote snapshots listed by locally cached
> {{maven-metadata-*.xml}} will always be selected regardless of their relative
> age compared to any locally installed snapshots. To repro:
> a) "mvn deploy" lib-a
> b) wait a few seconds
> c) "mvn install" lib-a, this creates a local snapshot that is newer than the
> remote snapshot
> d) in a dependent project lib-b, "mvn compile -U"
> The -U flag to enforce metadata download is rather crucial as otherwise the
> feature introduced for MNG-4326 hides the defect.
> Besides the expected download of the remote metadata, Maven erroneously also
> downloads/uses the outdated remote snapshots.
--
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
