Description Steffen Pingel 2012-01-24 06:41:46 EST

I have set the JVM to "Java 1.7" in the configuration of this job: https://hudson.eclipse.org/hudson/job/mylyn-builds-nightly/configure 

When the job executes Maven is spawned with Java 1.6 regardless:

[INFO] Using bundled Maven 3 installation
[INFO] Checking Maven 3 installation environment
[workspace] $ /opt/users/hudsonbuild/.hudson/maven/slavebundle/bundled-maven/bin/mvn --help
[INFO] Checking Maven 3 installation version
[workspace] $ /opt/users/hudsonbuild/.hudson/maven/slavebundle/bundled-maven/bin/mvn --version
[INFO] Detected Maven 3 installation version: 3.0.3
[workspace] $ /opt/users/hudsonbuild/.hudson/maven/slavebundle/bundled-maven/bin/mvn clean verify -V -e -Danalysis.skip=false -Dmaven.ext.class.path=/opt/users/hudsonbuild/.hudson/maven/slavebundle/resources:/opt/users/hudsonbuild/.hudson/maven/slavebundle/lib/maven3-eventspy-3.0.jar:/opt/users/hudsonbuild/.hudson/war/WEB-INF/lib/hudson-remoting-2.1.2.jar -Dhudson.eventspy.port=49683 -Dmaven.repo.local=/opt/users/hudsonbuild/.hudson/jobs/mylyn-builds-nightly/workspace/.maven/repo -f pom.xml -fae
[DEBUG] Waiting for connection on port: 49683
Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500)
Maven home: /opt/users/hudsonbuild/.hudson/maven/slavebundle/bundled-maven
Java version: 1.6.0_21, vendor: Sun Microsystems Inc.
Java home: /opt/public/common/sun-jdk1.6.0_21_x64/jre

If I add a shell call that invokes Java directly I get this:

+ java -version
java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)

But $JAVA_HOME still seems to point to a JDK 1.6:

+ echo /shared/common/sun-jdk1.6.0_21_x64
/shared/common/sun-jdk1.6.0_21_x64

I get the same results when running on master or a slave. 

Any ideas how to force Java 7 for the build?