[
https://issues.apache.org/jira/browse/CALCITE-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde resolved CALCITE-5098.
----------------------------------
Resolution: Fixed
Fixed in
[f48dbc8c|https://github.com/apache/calcite-avatica/commit/f48dbc8c10d761d52a289d37eaf8e52b90239fa6].
> Migrate Avatica to Gradle 7.4.2, and support Java 16 and 17
> -----------------------------------------------------------
>
> Key: CALCITE-5098
> URL: https://issues.apache.org/jira/browse/CALCITE-5098
> Project: Calcite
> Issue Type: Bug
> Components: avatica
> Reporter: Julian Hyde
> Assignee: Julian Hyde
> Priority: Major
> Fix For: avatica-1.21.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Before this change, Avatica used Gradle 6.8.1 and supported Java versions up
> to 15. After this change Avatica uses Gradle 7.4.2 and supports Java versions
> up to 17.
> Rationale: Gradle 6 only supports Java versions up to 15. For Java 16 we need
> to upgrade to Gradle 7. Java 17 requires Gradle 7.3. (See CALCITE-4829, the
> corresponding Calcite issue.)
> Gradle 7 removes support for the "testClasses" configuration, so we will need
> to remove uses of that, and we need to prevent uses of tests in one module by
> tests in another. In Calcite we solved that problem by creating a testkit
> module (see CALCITE-4821) but we don't go that far for Avatica. In the [dev
> branch|https://github.com/julianhyde/calcite-avatica/tree/5098-gradle-7]
> you'll see I created a testkit module but then removed it as overkill.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
