On 29/12/2010, at 1:36 AM, Russel Winder wrote: > Adam, > > On Tue, 2010-12-28 at 07:09 +1100, Adam Murdoch wrote: >> >> On 28/12/2010, at 7:06 AM, Munoz, Pablo [Tech] wrote: >> >>> Is there a way to set ivy caches [1] in gradle? >> >> >> There isn't at the moment. >> >> >> I'm curious, why do you want to configure the ivy cache? > > I am not sure about OP's situation but I find the ever increasing (and > all to often hugely out of date) cache of Maven, Ivy, Gradle, Grapes, > etc. a real irritation. I regularly end up simply deleting the whole > thing when I know I am on a high speed connection simply to get rid of > all the dross. > > Gradle/Ivy is particularly prone to leaving thousands of files in > ~/.gradle/cache called resolved-* and I often have to go in and delete > them. This is irritating. There should be a way of keeping the cache > clean apart from manual intervention. > > Tidying up ~/.gradle/cache/*/* to remove all the outdated rubbish is > also an extremely length and tedious operation.
I agree. So far, we've put no effort into garbage collecting the stuff that Gradle caches in ~/.gradle and $projectDir/.gradle. The plan at this stage is to have the daemon periodically clean stuff up, and possibly some way to trigger this manually. Before doing so, I'd like to replace the ivy cache implementation, so that we use a unified caching mechanism internally. -- Adam Murdoch Gradle Developer http://www.gradle.org CTO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz
