I also noted that on a big multiproject build because I was reloading ivy in each sub-project. Fixing that solved my problem.
Gilles 2007/6/21, Jeffrey Blattman <[EMAIL PROTECTED]>:
yes we've seen this. i am not sure it has anything to do w/ Ivy. it is well noted that the ant and antcall tasks are memory intensive as they created new classloaders. you can get around this by increasing the permgen space for java when you run ant ... $ export ANT_OPTS="$ANT_OPTS -Xmx512m -XX:MaxPermSize=256m" you can probably make do w/ something <256M, but it depends on your build. Steve Loughran wrote: > > We're running out of memory in a big multi-module build, using rmic > and ivy; its <ivy:configure /> or <rmic> that things break. I've tried > ivy 1.4.1 and 2.0.0-alpha1. > > > 1. has anyone else encountered memory consumption problems (out of > permgenspace)? > 2. this seems most common on java1.6. > > I'm not sure that ivy is the problem here, we will have to track it > down (somehow), and am just checking before doing anything else (like > profiling the build) >
-- Gilles SCOKART
