calcite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Elser <>
Subject Heads-up: Avatica now "disconnected" from root project (Fwd: [jira] [Resolved] (CALCITE-1078) Move all Avatica module into a detached directory)
Date Mon, 07 Mar 2016 18:32:41 GMT
Hi all --

Just a warning, with this commit, Avatica is no longer attached to the 
main Calcite build. I'm deploying a build of 1.7.0-SNAPSHOT as I type, 
so, hopefully, no one should see any issues with this (as long as you're 
connected to the internet).

Things will be a little weird until we get 1.7.0 out (local changes to 
Avatica won't be directly represented in a "Calcite" build unless you 
install them first), but hopefully this will just be a temporary issue. 
Please feel free to reach out if you run into any issues and let me know 
if there's any more documentation I can update to clarify.

- Josh

-------- Original Message --------
Subject: [jira] [Resolved] (CALCITE-1078) Move all Avatica module into a 
detached directory
Date: Mon, 7 Mar 2016 18:28:40 +0000 (UTC)
From: Josh Elser (JIRA) <>



Josh Elser resolved CALCITE-1078.
     Resolution: Fixed

Fixed in;a=commit;h=5cee486f3ad878275ffe67e67cd8593d6bcfd62d

> Move all Avatica module into a detached directory
> -------------------------------------------------
>                 Key: CALCITE-1078
>                 URL:
>             Project: Calcite
>          Issue Type: Sub-task
>          Components: avatica
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.7.0
> To decouple Avatica from the rest of Calcite, we need to restructure the location of
the Maven modules and the pom structure.
> Let's move all of the avatica modules into an "avatica/" directory at the root of the
Calcite repository. We should also directly use the Apache parent pom instead of the Calcite
parent pom.

This message was sent by Atlassian JIRA

View raw message