You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Leo Simons <ma...@leosimons.com> on 2007/07/08 14:13:37 UTC
size of java cache dirs - .ivy is huge!
Of interest:
root@vmgump:/home/gump# cd ~gump
root@vmgump:/home/gump# du -hs .ivy
1.2G .ivy
root@vmgump:/home/gump# du -hs .maven
41M .maven
root@vmgump:/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: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: ant-contrib seems to be building with stale snapshot
Posted by Bill Barker <wb...@wilshire.com>.
I've wiped the checkout for ant-contrib on vmgump, so Gump will have to do a
fresh co on the next cycle. There was a problem that the ~gump/.ivy
directory wasn't owned by 'gump', which was causing ivy failures.
"Stefan Bodewig" <bo...@apache.org> wrote in message
news:y1uir7x9psg.fsf@v30161.1blu.de...
> On Thu, 2 Aug 2007, Curt Arnold <ca...@apache.org> wrote:
>
>> The output for ant-contrib's Gump doesn't seem consistent with the
>> current build.xml file.
>
> Seems to be OK now.
>
>> A few days ago, I moved some things around in the ant-contrib
>> repository and updated the gump descriptors for ant-contrib and
>> cpptasks.
>
> This may as well be a case of anon svn access to sf.net lagging
> behind. Woudn't be the first time ...
>
>> Unfortunately, it looks like Gump is not updating from the new
>> location. Could someone blow away the ant- contrib and cpptasks
>> checkouts?
>
> I haven't changed anything, but it seems to be fine now. Or isn't it?
>
> Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: ant-contrib seems to be building with stale snapshot
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 2 Aug 2007, Curt Arnold <ca...@apache.org> wrote:
> The output for ant-contrib's Gump doesn't seem consistent with the
> current build.xml file.
Seems to be OK now.
> A few days ago, I moved some things around in the ant-contrib
> repository and updated the gump descriptors for ant-contrib and
> cpptasks.
This may as well be a case of anon svn access to sf.net lagging
behind. Woudn't be the first time ...
> Unfortunately, it looks like Gump is not updating from the new
> location. Could someone blow away the ant- contrib and cpptasks
> checkouts?
I haven't changed anything, but it seems to be fine now. Or isn't it?
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
ant-contrib seems to be building with stale snapshot
Posted by Curt Arnold <ca...@apache.org>.
The output for ant-contrib's Gump doesn't seem consistent with the
current build.xml file. A few days ago, I moved some things around
in the ant-contrib repository and updated the gump descriptors for
ant-contrib and cpptasks. Unfortunately, it looks like Gump is not
updating from the new location. Could someone blow away the ant-
contrib and cpptasks checkouts?
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: size of java cache dirs - .ivy is huge!
Posted by Steve Loughran <st...@apache.org>.
Leo Simons wrote:
>
> * we must erase ~/.ivy after every run
>
> opinions?
You also need to purge ~/.ivy2
Ivy has just moved to a new location because they use different XML
files, and want to avoid conflict
--
Steve Loughran http://www.1060.org/blogxter/publish/5
Author: Ant in Action http://antbook.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: size of java cache dirs - .ivy is huge!
Posted by Steve Loughran <st...@apache.org>.
Leo Simons wrote:
> Of interest:
>
> root@vmgump:/home/gump# cd ~gump
> root@vmgump:/home/gump# du -hs .ivy
> 1.2G .ivy
> root@vmgump:/home/gump# du -hs .maven
> 41M .maven
> root@vmgump:/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?
+1 to killing ivy and .m2 regularly
I've just tweaked my gump target to run our ivy-purge target before each
gump build; this pulls all smartfrog artifacts from ~/.ivy/published
and ~/.ivy/cache ; its what we do before releases to make sure there
isnt any legacy state in there. I could add something similar for the m2
repository. This will stop smartfrog leaking versions, though gump is
still vulnerable to anything else publishing in to ivy
-steve
--
Steve Loughran http://www.1060.org/blogxter/publish/5
Author: Ant in Action http://antbook.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: size of java cache dirs - .ivy is huge!
Posted by Steve Loughran <st...@apache.org>.
Bill Barker wrote:
> "Leo Simons" <ma...@leosimons.com> wrote in message
> news:BC90CF10-AB1E-485C-85FD-116C2B578E34@leosimons.com...
>> Of interest:
>>
>> root@vmgump:/home/gump# cd ~gump
>> root@vmgump:/home/gump# du -hs .ivy
>> 1.2G .ivy
>> root@vmgump:/home/gump# du -hs .maven
>> 41M .maven
>> root@vmgump:/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.
>>
>
> I disabled the cleanup for .maven, since it nuked all of the plugins maven
> needs to do anything. We run maven with --offline, so it shouldn't grow too
> big.
What about purging *-SNAPSHOT in the maven dir?
--
Steve Loughran http://www.1060.org/blogxter/publish/5
Author: Ant in Action http://antbook.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: size of java cache dirs - .ivy is huge!
Posted by Bill Barker <wb...@wilshire.com>.
"Leo Simons" <ma...@leosimons.com> wrote in message
news:BC90CF10-AB1E-485C-85FD-116C2B578E34@leosimons.com...
> Of interest:
>
> root@vmgump:/home/gump# cd ~gump
> root@vmgump:/home/gump# du -hs .ivy
> 1.2G .ivy
> root@vmgump:/home/gump# du -hs .maven
> 41M .maven
> root@vmgump:/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.
>
I disabled the cleanup for .maven, since it nuked all of the plugins maven
needs to do anything. We run maven with --offline, so it shouldn't grow too
big.
> cheers,
>
> Leo Simons
> --
> http://www.leosimons.com/blog/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org