[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546997#comment-14546997 ]
Mike Matrigali commented on DERBY-6809: --------------------------------------- Not sure what exactly is being proposed. At one point in the past derby supported jdk14, but had jdk15 features that were enabled if you were running against a jdk15 jvm. If the file needed to be compiled with jdk15 compiler there was a mechanism in the build files to let the system know that. It is up to the developer of the code to make sure system still runs with existing capability if running on jdk14. There are mechanisms supported by the derby class loader to allow system to determine jvm level and then to load either a jdk14 or jdk15 version of the code that would implement the same interfaces. If what is being proposed is to desupport running with jdk17 and earlier versions of the jvm, in the past derby has given users at least a one release warning. The types of thing being proposed sound like features to me so should only be added to a future major release, not to the existing 10.11 release. > 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.3.4#6332)