It's a known issue of the new "Wharf" cache implementation (see GRADLE-1723). I recommend to stay with milestone 3 for the time being.
-- Peter Niederwieser Principal Engineer, Gradleware http://gradleware.com Creator, Spock Framework http://spockframework.org Twitter: @pniederw Russel Winder wrote: > > I have a project that builds fine with Groovy 1.8.0 being the version of > Groovy depended on by the project. As soon as I change this to 1.8.1 -- > no other changes -- Gradle goes into a sequence of 5-10 minute pauses, > then issues a > > impossible to acquire lock for org.codehaus.groovy#groovy-all;1.8.1 > > The upshot is that a build that takes about 15s to succeed turns into a > 1hour later it tells you its a failed build. > > This is with Gradle 1.0-rc-1-20110812093853+0100 I also get this with > 1.0-milestone-4, but not with 1.0-milestone-4-20110725000027+0200 > > -- > Russel. > ============================================================================= > Dr Russel Winder t: +44 20 7585 2200 voip: > sip:[email protected] > 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] > London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder > -- View this message in context: http://gradle.1045684.n5.nabble.com/Gradle-and-Groovy-1-8-1-tp4693362p4694121.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
