You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2018/02/28 05:18:00 UTC

[jira] [Closed] (CALCITE-1162) Rework travis to not build "core" or "avatica" as necessary

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

Julian Hyde closed CALCITE-1162.
--------------------------------

> Rework travis to not build "core" or "avatica" as necessary
> -----------------------------------------------------------
>
>                 Key: CALCITE-1162
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1162
>             Project: Calcite
>          Issue Type: Improvement
>          Components: build
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Trivial
>
> As I'm working on a new Avatica pull-request, I'm seeing that travis is still building the rest of Calcite. This used to be reasonable before we had the first release of Avatica, but now it's just unnecessary.
> Maybe there's a way we can determine when changes are for Avatica only or Calcite only (with a rare case of both, e.g. pom plugin configuration changes?)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)