|
||||||||
|
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/d/optout.
Compiling with a different JDK with different API is not really an option for building productive release code (ok, it should not use such a outdated JDK either). Unfortunately I also use the maven release plugin a lot, this can afaik not be emulated easily by a freestyle job.
For me the severity is actually blocker because I have a whole bunch of these jobs. The fix of
JENKINS-18403from Jesse Glick sounded like a reliable way to support older JDKs without the need that the Jenkins code itself needs to be 1.4 compatible forever.