|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-14127) Support L... [email protected] (JIRA)
- [JIRA] (JENKINS-14127) Supp... [email protected] (JIRA)
- [JIRA] (JENKINS-14127) Supp... [email protected] (JIRA)
- [JIRA] (JENKINS-14127) Supp... [email protected] (JIRA)
- [JIRA] (JENKINS-14127) Supp... [email protected] (JIRA)
- [JIRA] (JENKINS-14127) Supp... [email protected] (JIRA)

Interesting
snippets from the Jenkins POM [1]: lines 558-9 set the source and target Java versions to 1.5, but then in lines 578-81 we find
<!-- There is a bug in JDK 1.5's compiler therefore need to compile with 1.6 -->
<requireJavaVersion>
<version>1.6.0-18</version>
</requireJavaVersion>
So if Jenkins seemingly requires a 1.6 compiler to be built, it shouldn't be a problem to build it with source and target versions of 1.6.
I understand Monty's point about compatibility but from this it would seem that a split build should not require any code changes...
[1] https://github.com/jenkinsci/jenkins/blob/master/pom.xml