[
http://jira.codehaus.org/browse/MNG-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87605
]
David Hay commented on MNG-2434:
--------------------------------
We see this behavior as well in Maven 2.0.4. If a new SNAPSHOT version of an
artifact is deployed to the remote repository and then I do a 'mvn install' of
the same artifact, building a project that depends on that SNAPSHOT will use
the version in the remote repository instead of the one I just installed into
my local repository (which is newer than the one on the remote repository)
> Local snapshots should be preferred over remote ones
> ----------------------------------------------------
>
> Key: MNG-2434
> URL: http://jira.codehaus.org/browse/MNG-2434
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.4
> Reporter: Carsten Ziegeler
>
> If you're build a project with snapshots, m2 tries to download the newest
> versions of the snapshots even if the local ones are newer. Interestingly
> later on, the local versions are used. So the download is useless.
> A complex test case for this is the Cocoon project where nearly all modules
> are snapshot and locally build.
--
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
