[ http://jira.codehaus.org/browse/MNG-2434?page=comments#action_70099 ] Carsten Ziegeler commented on MNG-2434: ---------------------------------------
I don't think that this is a dupe: It really downloads the artifacts sometimes not just the poms. We are using the plain SNAPSHOT version. Now perhaps the interesting part is that this happens during a build where these artifacts have just been created and put in the local repository. So a simplified example is, you have two modules A and B, both have the version as SNAPSHOT and B depends on A. Now you build both modules at once, first A gets build and is installed in the local repo, then B gets build, downloads a snapshot of A from the remote server, builds and then uses the local version of B. I'm not exactly sure of this last part, but upto now, everytime changes locally done to A where available in B although B downloaded a SNAPSHOT of A which could not have these local changes. This does not happen always, but from time to time. > 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
