See <
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/Weld-2.x-api-nightly/...
------------------------------------------
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on dev01-rhel5-x86 in workspace
<
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/Weld-2.x-api-nightly/...
Checkout:Weld-2.x-api-nightly /
<
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/Weld-2.x-api-nightly/... -
hudson.remoting.Channel@1bc89221:dev01-rhel5-x86
Using strategy: Default
Last Built Revision: Revision bd83c2343ca871a95247827929193c60c4445810 (origin/master)
Fetching changes from 1 remote Git repository
Fetching upstream changes from origin
Commencing build of Revision bd83c2343ca871a95247827929193c60c4445810 (origin/master)
Checking out Revision bd83c2343ca871a95247827929193c60c4445810 (origin/master)
[Weld-2.x-api-nightly] $ /qa/tools/opt/apache-maven-3.0.3/bin/mvn -f api/pom.xml
-Dmaven.test.failure.ignore=true
-Dmaven.repo.local=/qa/home/hudson/private_maven_repos/weld clean deploy -U
/qa/tools/opt/apache-maven-3.0.3/bin/mvn: line 167: /qa/tools/opt/jdk1.7.0_last/bin/java:
cannot execute binary file
/qa/tools/opt/apache-maven-3.0.3/bin/mvn: line 167: /qa/tools/opt/jdk1.7.0_last/bin/java:
Success
Build step 'Invoke top-level Maven targets' marked build as failure