|
||||||||
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.
Unfortunatelly I got stuck at the same Error Message too.
As Java 6 introduces incompatible changes in the JDBC API, we have JDK 1.5 jobs using the Maven Project plugin and the m2release plugin.
Fortunatelly there are only a few jobs left and I will try to force development to get rid of this usage, but nevertheless at the moment its a blocker to move beyond Jenkins LTS 1.565.2
The workaround to set something like $JDK_5_HOME, how is this working, because in the Jenkins Maven Project Job Config I still would need to use JDK 1.6+, wouldn't I?