[
https://issues.apache.org/jira/browse/CALCITE-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179410#comment-15179410
]
Josh Elser commented on CALCITE-1077:
-------------------------------------
Started working on this tonight and I have an outline up
https://github.com/joshelser/calcite/tree/1077-avatica-detach.
I need to look at it with fresh eyes again, but I don't think it's too bad for
a first pass. I'll have to run through a mock release process for Avatica to
make sure it's generating reasonable artifacts (I'm not sure yet), checking
Javadocs too. The usual.
There's a bit of duplication in checkstyle configuration files, but I think
that's more of an issue with how the "core" build is doing it
(https://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html
is what's recommended). That could just be something to change in the future.
The checkstyle rules haven't been changing *too* much.
> Separate Avatica from "core" Calcite build
> ------------------------------------------
>
> Key: CALCITE-1077
> URL: https://issues.apache.org/jira/browse/CALCITE-1077
> Project: Calcite
> Issue Type: Task
> Components: avatica
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: 1.7.0
>
>
> Uber-JIRA-issue for tracking the separation of Avatica from the rest of the
> Calcite build.
> Long term, Avatica can be a standalone project, but we're not there yet in
> terms of governance (enough people intimately involved). One thing we can do
> now is to separate Avatica from Calcite and begin "getting them used to" not
> being next to one another.
> DISCUSS thread:
> https://mail-archives.apache.org/mod_mbox/calcite-dev/201601.mbox/%3C56ABCCFF.3010205%40gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
