[
https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273660#comment-16273660
]
Rick Hillegas commented on DERBY-6809:
--------------------------------------
Q> Also, does derby still compile to Java 6 bytecode or now say 10.15 will
always compile to Java 9 bytecode? I assume the later.
A> 10.15 compiles into Java 9 bytecode.
Q> Another suggestion, can 10.15 be a long term supported release. As in,
future bug fixes and features will be available for this release too.
Backported if you can say so.
A> For the past several years, Derby has produced a new release family (10.12,
10.13, 10.14) once a year, often with a maintenance release roughly half way
inbetween. Once we move onto the next release family, there is little
motivation to produce an official maintenance release on any earlier family.
However, bug fixes can be (and often are) ported to older release families.
Anyone can build a distribution from one of these patched families. If you are
concerned about a particular bug fix, please let the committers know so that
they can backport the fix to the target you need.
Q> I assume that we are dropping support for older JAVA versions but not
necessarily rewriting the code to support and take advantages of new features
in JAVA latest versions.
A> I'm not aware that anyone is working on a large-scale re-write of the
existing code base in order to take advantage of new Java features. However,
the code was rototilled significantly so that it compiles cleanly, without
warnings, under Java 9. Contributors do take advantage of new language features
when writing new code, of course.
Q> Essentially this will help interested developers do try and rewrite DERBY
code to take advantage of newer features.
A> Derby is already divided fairly cleanly into independent components.
Hopefully, that component architecture will become clearer and cleaner as we
proceed with our effort to divide 10.15 into Jigsaw-ready modules. If you are
planning to re-write the Derby code, I highly recommend that you design your
changes so that your new code will appear as a new implementation of an
existing component. That will make it easier to evaluate and package your
changes as the community accepts them.
Thanks,
-Rick
> Java 1.8 feature use
> --------------------
>
> Key: DERBY-6809
> URL: https://issues.apache.org/jira/browse/DERBY-6809
> Project: Derby
> Issue Type: Improvement
> Components: Network Server
> Affects Versions: 11.0.0.0
> Reporter: sagar
>
> Suggestion ...
> Is it possible to auto modify the existing source code using tools like
> Netbeans, and take advantage of the new features in JDK 1.8 for better
> multiuser performance and better utilization of current day multicore
> processors?
> Plainly put, can we have from 11.0 onwards a version of derby which takes
> advantage of the advancements and new features in java 1.8 ...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
