It seems this is because exoPackage calls many times maven in the same VM to do dependency:get and there is a memory leak.
On Fri, 2009-10-30 at 16:25 +0100, Arnaud HERITIER wrote:full build log attached.
> I didn't try for several weeks.
> I don't remember to already had this issue.
> Can you send me in private the full log. Perhaps I'll see something.
>
> Arnaud
>
> On Fri, Oct 30, 2009 at 3:10 PM, Matt Wringe <mwringe@redhat.com>
> wrote:
> Has anyone experienced problems when trying to build gatein
> using a
> clean (ie empty) maven repo?
>
> I can build the portal part fine, but when I go to package the
> portal I
> run into some issues. The packaging build claims it was
> successful, but
> there are error message like these in the logs:
>
> > [INFO] [INFO]
> ------------------------------------------------------------------------
> > [INFO] [ERROR] FATAL ERROR
> > [INFO] [INFO]
> ------------------------------------------------------------------------
> > [INFO] [INFO] Java heap space
> > [INFO] [INFO]
> ------------------------------------------------------------------------
> > [INFO] [INFO] Trace
> > [INFO] java.lang.OutOfMemoryError: Java heap space
>
> This will cause that part of the build to stop, but it still
> continues
> with the other part of the build and claims at the end that
> the build is
> successful when its not.
>
> This only occurs with a fresh maven repo and the Java heap
> space issue
> occurs after its been downloading artifacts for a while. The
> downloading
> of artifacts is also really slow and strange for the packaging
> part.
>
> Has anyone else experience this? Or is it only me?
>
> On Linux with JDK 1.6 and Maven 2.2.1
>
> _______________________________________________
> gatein-dev mailing list
> gatein-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/gatein-dev
>
>