On 7/8/07, Maarten Coene <[EMAIL PROTECTED]> wrote:
Any idea how we can help the gump people?
I think erasing the ivy cache after each run is the best option. We should also tell Leo that Ivy supports kind of SNAPSHOT versions (with changing = true), but it's up to the user to make the choice. Do you take care of answering them? Or do your prefer I do so? Xavier --
Maarten ----- Forwarded Message ---- From: Leo Simons <[EMAIL PROTECTED]> To: Gump code and data <[EMAIL PROTECTED]> Sent: Sunday, July 8, 2007 2:13:37 PM Subject: size of java cache dirs - .ivy is huge! Of interest: [EMAIL PROTECTED]:/home/gump# cd ~gump [EMAIL PROTECTED]:/home/gump# du -hs .ivy 1.2G .ivy [EMAIL PROTECTED]:/home/gump# du -hs .maven 41M .maven [EMAIL PROTECTED]:/home/gump# du -hs .m2 791M .m2 While we have a bunch of different stuff in .maven and .m2, almost all of the stuff in ~gump/.ivy is smartfrog artifacts, going back months and months and months. There's no reason for gump to keep months of generated jars. I'd argue that either * there must be a way to configure ivy to do a "SNAPSHOT" thingie or * we must erase ~/.ivy after every run opinions? Actually, I guess we could also just erase .maven and .m2, once a week, too. cheers, Leo Simons -- http://www.leosimons.com/blog/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ____________________________________________________________________________________ Shape Yahoo! in your own image. Join our Network Research Panel today! http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7
-- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://incubator.apache.org/ivy/ http://www.xoocode.org/
