[
https://issues.apache.org/jira/browse/CALCITE-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16375863#comment-16375863
]
Michael Mior commented on CALCITE-1162:
---------------------------------------
I'm guessing this is resolved now that Avatica is in a separate repo?
> 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)
