[
https://issues.apache.org/jira/browse/CALCITE-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308265#comment-17308265
]
Julian Hyde commented on CALCITE-4547:
--------------------------------------
{quote}It might be time to use
https://docs.gradle.org/6.8.3/userguide/toolchains.html to decouple java which
is used to launch Gradle from java which is used to build and execute
tests{quote}.
Well, maybe. But I don't think it's good to build Calcite on only one JDK
version. I think it's good that Calcite should build on ANY supported JDK
version. So, if we use Gradle toolchains we'd have to invent another forcing
function to force us to get the code compiling under JDK 16.
> Support Java 16
> ---------------
>
> Key: CALCITE-4547
> URL: https://issues.apache.org/jira/browse/CALCITE-4547
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Support building and running on [Java 16|https://jdk.java.net/16/] (OpenJDK
> 16).
> This will require an [upgrade to Gradle
> 7|https://melix.github.io/blog/2021/03/gradle-java16.html], because Gradle 6
> will not support Java 16.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
