[
https://issues.apache.org/jira/browse/CALCITE-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16236632#comment-16236632
]
Julian Hyde commented on CALCITE-2027:
--------------------------------------
Let's consider upgrading other components as well. Staying up to date reduces
the chances we run into a security issue. Runtime components:
* prefer guava-21 (but continue to support as early as guava-14.0.1)
* prefer jdk-9 (but continue to support 8)
* upgrade to jetty-9.3.8.v20160314 (from jetty-9.2.15.v20160210)
* upgrade to jackson-2.6.5 (from jackson-2.6.3)
* upgrade to janino-2.7.8 (from janino-2.7.6)
Build and testing components:
* prefer maven-3.5.x (but continue to support maven-3.3.x)
* upgrade to java-diff-1.1.1 (from java-diff-1.1)
* upgrade to h2-1.4.196 (from h2-1.4.185)
* upgrade to hsqldb-2.4.0 (from hsqldb-2.3.1)
* upgrade to javacc-maven-plugin-2.6 (from 2.4)
* upgrade to forbiddenapis-2.4.1 (from 2.3)
Also, start thinking about obsoleting joda. (People can use java.time instead
since we've dropped JDK 7.)
Look for and replace "javase/7" in URLs (.java and .md files).
> Drop support for Java 7 (JDK 1.7)
> ---------------------------------
>
> Key: CALCITE-2027
> URL: https://issues.apache.org/jira/browse/CALCITE-2027
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
>
> Drop support for Java 7 (also known as JDK 1.7):
> * The code would no longer compile under JDK 7
> * Compiler would have source 1.8 target 1.8
> * Class files would run on JDK 8 and higher
> * Developers can use Java 8 syntax such as lambdas and default methods
> We would continue to build and run under JDK 8 and 9.
> I think it would be best to wait a while before converting existing code to
> Java 8 style (e.g. converting SAM anonymous classes to lambdas) because code
> changes might be extensive.
> I expect there will be cases that we want to change interfaces so that they
> are easier to use as lambdas. Let's make those changes cautiously when we
> come across them, and mark existing interfaces and methods deprecated until
> we remove them in 2.0.
> Let's give at least one release notice of this change. In 1.15 (the next
> release) let's announce that this will be the last release that supports Java
> 7. So this will be fixed for 1.16.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
