[CALCITE-1077] Separate Avatica from "core" Calcite build

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: avatica-1.7.0, 1.7.0
• Component/s: avatica
• Assignee: Josh Elser
• Reporter: Josh Elser
• Created: 04/Feb/16 17:15
• Updated: 14/Mar/16 15:07
• Resolved: 10/Mar/16 01:48

Description

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

Issue Links

• links to: PR

Sub-Tasks

• Move all Avatica module into a detached directory: Closed
• Update website for Avatica: Closed
• Update CI tasks for new Avatica location: Closed
• Update artifactId and name for avatica modules: Closed
• RAT check failure on Calcite due to avatica directory: Closed
• Exclude Avatica from calcite src release assembly descriptor: Closed
• Add KEYS file to maintain consistency with Calcite build: Closed
• Update website properly for Avatica 1.7.0: Closed
• Update minor.version from 6 to 7: Closed
• Create a README.md for Avatica: Closed
• Remove incorrect NOTICE paragraph in Avatica: Closed
• Fix Avatica LICENSE file: Closed
• Remove protobuf from Calcite's LICENSE: Closed