[JIRA] [core] (JENKINS-26078) "Path to java executable" issue with Java 8 on Windows slave

[davida2...@java.net (JIRA)]

davida2009 created JENKINS-26078 "Path to java executable" issue with Java 8 on Windows slave Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Dec/14 10:59 AM Description: It seems that Oracle's Java 8 installer for Windows uses symlinks to specify the locations of the java executables: C:\>dir \ProgramData\Oracle\Java\javapath Directory of C:\ProgramData\Oracle\Java\javapath 15/12/2014 10:41 <DIR> . 15/12/2014 10:41 <DIR> .. 15/12/2014 10:41 <SYMLINK> java.exe [C:\Program Files\Java\jre1.8.0_25\bin\java.exe] 15/12/2014 10:41 <SYMLINK> javaw.exe [C:\Program Files\Java\jre1.8.0_25\bin\javaw.exe] 15/12/2014 10:41 <SYMLINK> javaws.exe [C:\Program Files\Java\jre1.8.0_25\bin\javaws.exe] The actual path to javaw.exe is now: "C:\Program Files\Java\jre1.8.0_25\bin\javaw.exe" To make this work with Jenkins, we have to add "C:\Program Files\Java\jre1.8.0_25\bin" to the system path so that Jenkins can find javaw.exe. I think a more correct way would be to specify: "C:\ProgramData\Oracle\Java\javapath\javaw.exe" in the "Path to java executable" field of the slave's configuration. But, if I do that, the slave fails to launch and spins at: Connecting to tmsd409 Checking if Java exists Jenkins-slave.xml on the slave shows: <executable>javaw.exe</executable> So my specified Java path appears not to be copied to the slave. Is this a bug? Project: Jenkins Priority: Minor Reporter: davida2009

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.