|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
It looks like the issue exists on Jenkins ver. 1.550 on Windows 2008 R2 slave (JDK 7u51, JAVA_HOME is set to C:\Program Files\Java\jdk1.7.0_51). On Jenkins master node (Debian 7.2) in JDK section in configuration settings there's no JDK defined. I duplicated JAVA_HOME variable in slave node representation settings but without any success either (I restarted Jenkins and slave connections several times (both jnlp and java -jar don't work anyway)) -maven build still fails.
The work-around for users who don't rely on JDK version is to copy lib folder to path provided in error msg (in my case it was C:\Program Files\Java\lib).