Nope, I have configured several JDKs and the job's configured JDK is not picked up for all goals when you click on "Maven Perfom Release". (But the configured JDK is correctly picked up from when you are click on "Build now"). I studied the log file from "Maven Perform Release" a bit more and it seems that the release goals are using the right JDK (1.6.0_35), but not the verify goal (JDK 1.6.0_30)

"Maven Perform Release" log extract:
Executing Maven: -B -f D:/jenkins/workspace/eps-uposadapter-main/product/eps/adapters/uposadapter/main/pom.xml -DdevelopmentVersion=1.0.1-SNAPSHOT -DreleaseVersion=1.0.0 -X -Dresume=false release:prepare release:perform
+ Error stacktraces are turned on.
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_35
Java home: C:\java32\jdk1.6.0_35\jre
Default locale: sv_SE, platform encoding: Cp1252
OS name: "windows 7" version: "6.1" arch: "x86" Family: "windows"
....
[DEBUG] Executing: cmd.exe /X /C "D:\jenkins\tools\maven221\bin\mvn.bat -B -X -D maven.repo.local=D:\Work\LocalRepository -P alwaysOn,codesign clean verify"
[INFO] + Error stacktraces are turned on.
[INFO] Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
*[INFO] Java version: 1.6.0_30*
*[INFO] Java home: C:\Program Files\Java\jdk1.6.0_30\jre*
[INFO] Default locale: sv_SE, platform encoding: Cp1252

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to