On 7/9/07, Matthew Inger <[EMAIL PROTECTED]> wrote:
This something we already do in our company. In our ivyconf.xml:
<ivyconf>
<properties file="${ivy.conf.dir}/ivyconf.properties" override="false"
/>
<conf ... defaultCache="${cache.dir}" />
Then, our build software (quickbuild) has been configured to set the "
cache.dir" system
property. This allows us to pass in any directory to use as the ivy
cache. Works like a
charm, especially since we want our builds to have isolated cache areas
per build configuration.
Thanks for this experience feedback. I indeed favor this approach too. The
advantage of having one property usable to override the default cache
location whatever the settings are is that it could be used in continuous
integration server without even requiring to touch the settings.
Xavier
----
[EMAIL PROTECTED]
"Once you start down the dark path, forever will it
dominate your destiny. Consume you it will " - Yoda
----- Original Message ----
From: Maarten Coene <[EMAIL PROTECTED]>
To: [email protected]
Sent: Monday, July 9, 2007 10:00:17 AM
Subject: Re: Fw: size of java cache dirs - .ivy is huge!
Maybe we should allow gump to override the cache location of a project (
e.g. by passing a system-property to ant)?
e.g.: ant -f build.xml -Divy.cache=some_directory
No matter how the project tries to configure Ivy, Ivy always use this
cache directory...
Maarten
----- Original Message ----
From: Jeffrey Blattman <[EMAIL PROTECTED]>
To: [email protected]
Sent: Monday, July 9, 2007 2:51:17 PM
Subject: Re: Fw: size of java cache dirs - .ivy is huge!
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
>
>
>
>
____________________________________________________________________________________
Moody friends. Drama queens. Your life? Nope! - their life, your story.
Play Sims Stories at Yahoo! Games.
http://sims.yahoo.com/
____________________________________________________________________________________
Park yourself in front of a world of choices in alternative vehicles.
Visit the Yahoo! Auto Green Center.
http://autos.yahoo.com/green_center/
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://incubator.apache.org/ivy/
http://www.xoocode.org/
