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 Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
