Hudson uses the configured JDK for a maven build but does not set the JAVA_HOME property. So if you try to make a release the prepare is executed against the configured jdk but the perform is executed against the default JDK.

We have a couple of builds which depends on the IBM JDK. We have configured whe jobs appropriately and it is working for snapshot builds. When running a release build the JDK tomcat is running on (Sun JDK) is used instead.

When we set the JAVA_HOME explicitely in the job it works. But this is a mess as we have to enter the full path to the jdk (and this is not the same on all slaves).

Hudson should set JAVA_HOME for the current build or - at least - provide a variable which holds the path to the configured JDK.

This a blocking issue at our site!