Any chance we could see the full console log? Is the build running on the master or slave? How did you install Jenkins? Are you using the default maven that comes with Mac?
-- Sami Mark Cafaro <mark.caf...@gmail.com> kirjoitti 4.5.2012 kello 22.18: > Is anyone aware of a workaround for the Maven crash on Jenkin's build in OS X > that causes: > > <===[JENKINS REMOTING CAPACITY]===>channel started > ERROR: Maven JVM terminated unexpectedly with exit code 134 > > In the one blog post I can find about it, > http://samuraism.jp/blog/2010/12/16/hudson_build_fails_with_maven_jvm_terminated_unexpectedly_with_exit_code_134.html > , its claimed to be an issue with Apple's JVM. The suggested workaround is > to use -Djava.awt.headless=true but this does not solve the issue for me. > > Currently on Jenkins ver. 1.447.1, but I've been having this issue on prior > versions as well.
