On 8/28/2014 10:26 AM, Rick Hillegas wrote:
On 8/27/14 5:32 PM, Gary Gregory wrote:
Hi All,
Now that DERBY-6213 <https://issues.apache.org/jira/browse/DERBY-6213>
is in the books, is there any interest here in deprecating Java 6 in
favor of Java 7?
Gary
--
E-Mail: [email protected] <mailto:[email protected]> |
[email protected] <mailto:[email protected]>
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
<http://garygregory.wordpress.com/>
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Thanks for raising this issue, Gary. Oracle stopped creating public
releases of Java 6 last year:
http://www.oracle.com/technetwork/java/eol-135779.html. However, Oracle
continues to provide new releases of Java 6 for customers who buy
support contracts. I can't find any information on IBM's commitment to
Java 6. Maybe one of the IBM engineers can comment.
In the interests of reducing code/testing complexity, I'd be happy to
deprecate support for Java 6. When we deprecate a platform, we generally
produce one last feature release for it. It is that last release which
announces the deprecation. If we followed that convention, then next
year's 10.12 release would still support Java 6. The first release to
drop Java 6 support would be 10.13, due out in 2016 if we keep to our
usual release cadence.
What do other people think?
Thanks,
-Rick
We should eventually vote the issue, but for me I think rick's suggested
plan should be the quickest transition. It fits the model
that we have followed in the past, and allows warning to legacy
applications running against Derby that would like to continue to
upgrade their db software but may not be ready to upgrade their JVM.
I would support a vote that announced deprecation with 10.12 release,
and implemented with 10.13 (or any plan longer than this).
Are there "compile" level features that developers are looking for in
java7 and above? A lot of my users take much longer to upgrade their
database software, so I do work to backport fixes into older releases.
DERBY-6213 and follow on work that changed code made backports not apply
cleanly any more - which leads to more work and greater possiblity of
not correctly backporting changes. I would like to understand the
likely non-backward compatible changes that this change would bring about.
