[jira] [Commented] (CALCITE-2905) Migrate build system to Gradle

["Vladimir Sitnikov (JIRA)" <ji...@apache.org>]

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

Vladimir Sitnikov commented on CALCITE-2905:
--------------------------------------------

[~julianhyde], I agree the release is tricky, so I have created a stub release environment: https://github.com/vlsi/asflike-release-environment

It starts Git server, SVN server (for emulating https://dist.apache.org/repos/dist/), and Nexus stub (for emulating https://repository.apache.org).

> 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
>
> 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
(v7.6.3#76005)