[JIRA] [maven2] (JENKINS-6763) Hudson does not set JAVA_HOME for Maven Builds

Fri, 15 Aug 2014 10:57:52 -0700

 
Damon Overboe edited a comment on Bug JENKINS-6763

On Jenkins 1.575, working against Windows Server 2012, setting the JDK in Jenkins provides the option to input the JAVA_HOME variable, and that worked around the issue for me.

This might be what you were referring to as having it set twice, but given that it seems to completely ignore JAVA_HOME on the clients (even though it reports that correctly with the script console) it doesn't seem to cause any issues.

Here were my steps:

  1. Manage Jenkins
  2. Configure System
  3. Scroll to JDK installations
  4. Add JDK Installation
  5. Provide JAVA_HOME path to the JDK folder on the client/slave
    such as C:\Progra~2\Java\jdk1.7.0_67 where Proga~2 resolves to Program Files (x86)
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

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to