I've incorporated this change in 5e7b844b65cf021ce1378bc1a1f78f9bc8a2b33d toward 1.539

On 10/26/2013 01:35 PM, Kohsuke Kawaguchi wrote:
Since 1.520, we have been producing Jenkins core with Java6 class files,
but we haven't so far started using Java6 API so that we can go back to
Java5 compatibility in case there's a large uproar.

It's been cloes to 20 releases since then. While some users have noticed
this (JENKINS-18592 and JENKINS-16920), given the overwhelming support
in the dev list, library dependencies that require Java6, and existence
of workarounds, I think we should complete the Java6 migration by
finally lifting  "you can't rely on Java6 API" limitation.

Any objections?

[1]
https://groups.google.com/forum/#!topic/jenkinsci-dev/LOMtxbR0Elg/discussion
--
Kohsuke Kawaguchi

--
You received this message because you are subscribed to the Google
Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Jenkins Enterprise, our professional version of Jenkins

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to