Found the problem. The culprit seems to be Maven 2.0.7+. It has problems with SNAPSHOT dependency resolution with mirrorOf set tp *.
The solution is outlined here. http://www.jfrog.org/sites/artifactory/latest/maven.html I did as the post suggested and it worked. May be this should end up on the WIKI, or archiva proxy setup guide. thanks Brett Porter wrote: > > I've been seeing this also - I'm not yet sure of the conditions under > which they don't work. I have seen it work for the majority of > snapshots - but particularly those with long versions beforehand seem > problematic. > > I intend to investigate next week - if you can create an issue that'd > be helpful. > > Cheers, > Brett > > On 15/12/2007, gumnaam23 <[EMAIL PROTECTED]> wrote: >> >> I have setup Archiva Managed Internal Repository as my whole and sole >> mirror >> in my settings.xml. >> The settings.xml does not contain any other repository information, just >> the >> mirror entry . >> >> The Archiva Manged Internal Repository is set to proxy 4/5 external >> repositories, >> One of which contains certain SNAPSHOTs that I have as dependencies. >> >> The proxy connector for this repository has snapshot policy set to >> "always", >> I also tried >> "daily", "hourly". But the SNAPSHOT is never downloaded any my build >> fails. >> >> The log files show no special activity, how do I debug this issue ? >> -- >> View this message in context: >> http://www.nabble.com/Proxying-SNAPSHOT-repositories-tp14336170p14336170.html >> Sent from the archiva-users mailing list archive at Nabble.com. >> >> > > > -- > Brett Porter > Blog: http://www.devzuz.org/blogs/bporter/ > > -- View this message in context: http://www.nabble.com/Proxying-SNAPSHOT-repositories-tp14336170p14337896.html Sent from the archiva-users mailing list archive at Nabble.com.
