One thing to be aware of: as of M4 caches are now isolated per repository, meaning that you only ever have access to the cached artifacts for the declared repositories. In previous versions a single shared cache was used, similar to how Maven works. So previously you could fail to declare a required repository, but the artifacts could still be resolved as dependencies if they were in the cache.
On upgrade to M4, I experienced dependency resolution problems in one of my test build scripts: turns out that I was just relying on the slf4j and groovy dependencies being in the cache (which they were) and I was not declaring the repository required to find them. Upgrading to M4 forced me to add the required repository. Not sure if this is related to your problem (the "impossible to acquire lock" looks suspicious), but it's worth knowing when tracking down dependency resolution problems using M4. cheers Daz On 2 August 2011 16:00, Rene Groeschke <[email protected]> wrote: > Hi, > it fails in one of our mp builds. I wasn't able to cut it down to a small > reproducable example. Maybe I can get some more stacktraces, logs... Will > raise an issue after that. > > regards, > René > > Am 02.08.11 15:42, schrieb Peter Niederwieser: > > Sounds like a problem related to our new "Wharf" Ivy cache implementation. >> Please file a bug report. Can you provide us with a way to reproduce the >> problem? >> >> -- >> Peter Niederwieser >> Principal Engineer, Gradleware >> http://gradleware.com >> Creator, Spock Framework >> http://spockframework.org >> Twitter: @pniederw >> >> >> Rene Groeschke wrote: >> >>> after migrating our build from 1.0M3 to 1.0M4 one of our builds fails >>> the >>> error message "impossible to acquire lock for org.acme:SampleLib;1.03". >>> >>> Here is the full stacktrace: >>> -------------------- >>> ::::::::::::::::::::::::::::::**:::::::::::::::: >>> >>> :: UNRESOLVED DEPENDENCIES :: >>> >>> ::::::::::::::::::::::::::::::**:::::::::::::::: >>> >>> :: appframework#Appframework;1.**03: not found >>> >>> ::::::::::::::::::::::::::::::**:::::::::::::::: >>> >>> >>> :::: ERRORS >>> impossible to acquire lock for appframework#AppFramework;1.03 >>> >>> >> -- >> View this message in context: http://gradle.1045684.n5.** >> nabble.com/problems-with-**resolving-dependencies-after-** >> upgrade-to-1-0-M4-**tp4643418p4658756.html<http://gradle.1045684.n5.nabble.com/problems-with-resolving-dependencies-after-upgrade-to-1-0-M4-tp4643418p4658756.html> >> Sent from the gradle-user mailing list archive at Nabble.com. >> >> ------------------------------**------------------------------**--------- >> To unsubscribe from this list, please visit: >> >> >> http://xircles.codehaus.org/**manage_email<http://xircles.codehaus.org/manage_email> >> >> >> > > -- > ----------------------- > regards René > > rene groeschke > http://www.breskeby.com > @breskeby > > > > ------------------------------**------------------------------**--------- > To unsubscribe from this list, please visit: > > > http://xircles.codehaus.org/**manage_email<http://xircles.codehaus.org/manage_email> > > >
