dev@glassfish.java.net

Re: SIGSEGV when building v3

From: Jane Young <Jane.Young_at_Sun.COM>
Date: Tue, 18 Nov 2008 16:01:05 -0800

Are you sure?

I just tried building javaee-api first and then top level v3 and still
see jvm crash with SIGSEGV.
The only workaround I know that works is to execute "mvn .. install"
twice using the same maven repo.


Bill Shannon wrote:

> Jane Young wrote:
>
>> It's a known issue. See:
>> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6766662
>> Workaround is to rebuild again w/o cleaning up your maven repo.
>
>
> Still fails.
>
>
> Harsha Godugu wrote:
> > This is happening due to maven-bundle plugin hitting a vm limitation
> > around file manipulation (zip/jar files this case).
> > If you run into this issue, try first building javaee-api and then the
> > rest of the top level from v3/pom.xml.
>
> This worked for me.
>
>
> I also kicked the JDK team so hopefully this bug will get fixed in the
> next update release.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>