Hi Dawid, I'm pretty sure Uwe's wrong about that - e.g., it's possible to build projects from zero downloaded dependencies.
The sonatype repo declaration in the test-framework POM doesn't give an updatePolicy for releases, so the default policy, daily, is used. I think the updatePolicy is consulted only when an artifact has already been downloaded; when it isn't in the local repository, updatePolicy is ignored. In this case, v2.0.0 of randomizedtesting is missing from the local repo, so the sonatype repo should be checked; I don't understand why it wasn't. BTW, I get a 500 Internal Server Error when I visit <https://oss.sonatype.org/content/repositories/releases/org/carrot2/> with my browser. Maybe Maven actually attempted to contact sonatype repo, but doesn't report failed repo connections? Steve -----Original Message----- From: dawid.we...@gmail.com [mailto:dawid.we...@gmail.com] On Behalf Of Dawid Weiss Sent: Wednesday, September 05, 2012 7:50 AM To: dev@lucene.apache.org Subject: Re: [JENKINS-MAVEN] Lucene-Solr-Maven-4.x #87: POMs out of sync I don't understand maven: Uwe thinks it only checks the repository it already has an artifact from, is this true, Steven? Sonatype should be checked during this build but wasn't. We're still waiting for a sync with repo1. Dawid --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
