This is not uncommon for large multi-module builds. You need to increase the memory available for Maven, such as the heap depending on the error you're getting. Do this by setting the MAVEN_OPTS env variable.
My experience is that this is mainly due to the plugins being used in the build, not Maven core. Are you using Maven 3? Maven 3 core has a smaller memory footprint than Maven 2. /Anders On Sat, May 12, 2012 at 12:56 AM, Hilco Wijbenga <[email protected]> wrote: > Hi all, > > I have noticed that in a fairly large reactor build the build dies > close to the end (about 10 modules to go out of around 90). It simply > runs out of memory. Restarting it with -rf allows it to finish without > issues. There is a limit to how much memory I can give Maven... :-) > > So apparently, Maven does not release memory before continuing on with > the next module? Or would this be something that is specific to a > particular plugin (in my case, it's undoubtedly the GWT Maven plugin)? > > Cheers, > Hilco > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
