[
https://issues.apache.org/jira/browse/CALCITE-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17418741#comment-17418741
]
Vladimir Sitnikov commented on CALCITE-4789:
--------------------------------------------
[~asolimando], {{-Duser.timezone}} is not automatically passed to the test
execution.
The thing is that tests are runned in the forked JVM, so only the explicit set
of properties is passed there.
The properties are listed here:
https://github.com/apache/calcite/blob/4b1e9ed1a513eae0c873a660b755bb4f27b39da9/build.gradle.kts#L711-L726
I think we could add {{user.timezone}} there as well.
> Build is broken on Guava versions < 21
> --------------------------------------
>
> Key: CALCITE-4789
> URL: https://issues.apache.org/jira/browse/CALCITE-4789
> Project: Calcite
> Issue Type: Bug
> Environment: The build is currently broken on Guava versions 20 and
> lower. We claim in the release notes to support Guava 19 and higher.
> As part of this change, enable testing in CI of the lowest and highest
> supported Guava version. (We used to do this, but we stopped when we moved
> from Maven to Gradle. I still don't know how to set the Guava version from
> the Gradle command line.)
> Reporter: Julian Hyde
> Assignee: Julian Hyde
> Priority: Major
> Fix For: 1.28.0
>
>
> The build is broken on versions of Gradle less than 21. In our release notes
> we say we support Gradle 19 and higher.
> We used to test the supported range of Guava versions in CI. The fix for this
> issue must resume CI testing for the range of supported versions (currently
> 19.0 to 29.0-jre per
> [history.md|https://calcite.apache.org/docs/history.html] and 19.0 and higher
> per a comment in {{gradle.properties}}).
> How do I set the Guava version from the Gradle command line? I’d expect
> {code:java}
> ./gradlew -Dguava.version=19.0
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
