Le 06/02/13 19:39, Jesse Glick a écrit :
On 02/06/2013 06:12 AM, Martin Desruisseaux wrote:
the approach that we wanted to apply has been used for more than 5
years on Windows, Solaris, Linux Gentoo, Linux Ubuntu, MacOS, and
other Hudson/Jenkins servers without any JVM crash
Perhaps you were just lucky, or perhaps there is something in the
current Jenkins configuration that makes the crash more likely—for
example, if the job were marked as permitting multiple concurrent builds.
I will reiterate that while upgrading the Java 7 build is a good idea,
it will probably not affect this bug.
Well, we also have a JDK6 branch (namely "sis-trunk") built on the same
Jenkins server with the same configuration, and the JDK6 JVM never
crash. Admittedly the code - including the MOJO at cause - is slightly
different because of JDK7 features not supported in JDK6, but
nevertheless I'm somewhat optimist about the chances that upgrading the
JDK7 would help stabilizing the build.
In the main time, I tried to upgrade Maven from 3.0.3 to 3.0.4 and it
seems to have helped; the 5 last build have been stable.
Martin
