I discovered a simple way to develop and deploy the web site: $ cd calcite/site $ ln -s ../avatica/site avatica
then $ bundle exec jekyll serve as usual. The calcite site will be generated to calcite/site/target as usual, and the avatica site will be generated to calcite/site/target/avatica. I see the avatica site at http://localhost:4000/avatica/ <http://localhost:4000/avatica/>, as expected. Then we can “svn ci” files under calcite/site/target as usual. I think we should take this approach rather than doing what avatica/site/README.md currently recommends, which is to have a separate svn tree under avatica/site/target. I’ll quickly create a (bad) placeholder Avatica logo so that the sites are visually different. Julian > On Mar 7, 2016, at 10:49 AM, Julian Hyde <[email protected]> wrote: > > Thanks Josh, this is great. > > The next priority is to get an Avatica release 1.7.0 out. This needs to > happen before Calcite release 1.7.0, so that Calcite can depend on it. (The > release numbers are currently in sync but I expect them to drift apart over > time.) > > I saw you copied the web site wholesale. I presume plan to remove quite a lot > of it (e.g. the news posts). Shall we adopt a different color scheme for the > Avatica part of the site so that it’s visually different? > > I added a “powered by” page over the weekend, apparently after you’d copied > the site. Do you want Avatica and Calcite to share a Powered By page? (By > which I mean Avatica would not have its own Powered By page.) I guess that > the “Community” page should be shared (since we share a PMC, lists etc.) Are > there any other pages that should be shared? > > Can you re-visit the NOTICE file (the included software mentioned therein has > not been copied to Avatica). > > What’s the state of the build? Do you believe that Calcite and Avatica builds > are working right now? > > Julian > > > > >> On Mar 7, 2016, at 10:32 AM, Josh Elser <[email protected]> wrote: >> >> 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) <[email protected]> >> Reply-To: [email protected] >> To: [email protected] >> >> >> [ >> https://issues.apache.org/jira/browse/CALCITE-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel >> ] >> >> Josh Elser resolved CALCITE-1078. >> --------------------------------- >> Resolution: Fixed >> >> Fixed in >> https://git1-us-west.apache.org/repos/asf?p=calcite.git;a=commit;h=5cee486f3ad878275ffe67e67cd8593d6bcfd62d >> >>> Move all Avatica module into a detached directory >>> ------------------------------------------------- >>> >>> Key: CALCITE-1078 >>> URL: https://issues.apache.org/jira/browse/CALCITE-1078 >>> 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 >> (v6.3.4#6332) >
