[
https://issues.apache.org/jira/browse/CALCITE-5095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529981#comment-17529981
]
Stamatis Zampetakis commented on CALCITE-5095:
----------------------------------------------
Fixed in
https://github.com/apache/calcite-avatica/commit/360c0e7c84d754b7fffb64c0e021dbb1833ee283
for calcite-avatica.
> Support Java 18 and Guava 31.1-jre
> ----------------------------------
>
> Key: CALCITE-5095
> URL: https://issues.apache.org/jira/browse/CALCITE-5095
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Benchao Li
> Priority: Major
> Labels: pull-request-available
> Fix For: avatica-1.21.0, 1.31.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Java 18 is released as of 2022-03-22. Calcite should support it at compile
> time and run time.
> We should fix before Calcite release 1.31. To fix this, add JDK 18 to the CI
> targets in {{.github/workflows/main.yml}} and fix any errors/warnings. Modify
> {{site/_docs/howto.md}} and {{{}site/_docs/history.md{}}}.
> We should also fix before Avatica release 1.21. Let's use the same JIRA case
> for Avatica. To fix in Avatica, there will be similar changes to similar
> files.
> There is a new version of Guava (Calcite's current version is 30.0.1-jre, new
> version is 31.1-jre). It makes sense to upgrade Guava at the same time. IIRC
> you need to change {{{}main.yml{}}}, {{{}history.md{}}},
> {{{}gradle.properties{}}}.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
