[jira] [Commented] (CALCITE-4553) Use Gradle Toolchains for customizing JVM used for build and test Calcite

["Julian Hyde (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CALCITE-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308940#comment-17308940 ] 

Julian Hyde commented on CALCITE-4553:
--------------------------------------

As discussed in CALCITE-4547, I am fine with us using toolchains, but I would like the default JDK to be the user's JDK. That way, we have a clear forcing function - that when the user starts using JDK 16 (for instance), we build using JDK 16, and therefore discover any issues with the JDK 16 build.

> Use Gradle Toolchains for customizing JVM used for build and test Calcite
> -------------------------------------------------------------------------
>
>                 Key: CALCITE-4553
>                 URL: https://issues.apache.org/jira/browse/CALCITE-4553
>             Project: Calcite
>          Issue Type: Improvement
>    Affects Versions: 1.26.0
>            Reporter: Vladimir Sitnikov
>            Priority: Major
>
> [Gradle Toolchains|https://docs.gradle.org/6.8.3/userguide/toolchains.html] can use different JVM for Gradle execution and for the build process.
> It might help for testing newer Javas which are not yet supported for Gradle execution.
> For instance,  it can be "use the current JVM by default", and "use -PcalciteJavaHome=... JVM" if the property is added.
> Toolchains can be auto-provisioned, so it might simplify testing for the end-users.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)