it might be helpful to set defaultCache="..." so you can isolate / clean
the cache for a particular project. it's not friendly to remove
~/.ivy/cache, because you never know what the user is using it for.
Maarten Coene wrote:
Any idea how we can help the gump people?
--
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
