[
https://issues.apache.org/jira/browse/CALCITE-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003223#comment-17003223
]
Vladimir Sitnikov commented on CALCITE-2905:
--------------------------------------------
Does Flink work with that?
Do you mind contributing a PR that would add "test Flink with the latest
Calcite" like the following
[https://github.com/apache/calcite/blob/master/.github/workflows/main.yml#L55-L74]
?
In other words: "install Calcite to mavenLocal, checkout Flink, run some Flink
tests".
Does that make sense?
Then we'll know if Calcite changes affect Flink in future.
> Migrate build system to Gradle
> ------------------------------
>
> Key: CALCITE-2905
> URL: https://issues.apache.org/jira/browse/CALCITE-2905
> Project: Calcite
> Issue Type: Improvement
> Affects Versions: 1.18.0
> Reporter: Vladimir Sitnikov
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.22.0
>
> Attachments: image-2019-12-24-16-16-42-006.png,
> image-2019-12-24-16-18-51-071.png, image-2019-12-25-17-50-45-431.png
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Current build system has quirks, and it has well-known limitations.
>
> For instance:
> 1) If you change code in "core" and or "linq4j" modules and you want to check
> "cassandra", you need to "mvn install" those modules first otherwise
> "cassandra" would use "core" from the local Maven repository
> 2) If you want to see how Calcite plays together with Drill, it has to be
> multi-step as well. You can't just change some bits in Calcite and just
> build/test Drill
> 3) Maven builds seem to be single-threaded by default. For instance,
> checkstyle/forbiddenapis always goes before compile, and it does take time. I
> happen to disable checkstyle for local checks.
> 4) Maven plugins are hard to write. You can't just have a pair of classes to
> be used during the build.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
