[ 
https://issues.apache.org/jira/browse/CALCITE-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Sitnikov updated CALCITE-4553:
---------------------------------------
    Description: 
[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.

  was:
Gradle Toolchains 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.


> 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)

Reply via email to