You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@calcite.apache.org by Julian Hyde <jh...@apache.org> on 2016/03/07 19:49:25 UTC
Re: Heads-up: Avatica now "disconnected" from root project
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 <jo...@gmail.com> 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) <ji...@apache.org>
> Reply-To: dev@calcite.apache.org
> To: issues@calcite.apache.org
>
>
> [ 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)
Re: Heads-up: Avatica now "disconnected" from root project
Posted by Josh Elser <jo...@gmail.com>.
It had been causing me issues with the maven-release-plugin (at least
following the documented steps on the website).
It was causing the parent pom to try to fetch 1.7.0 versions of
artifacts that it hadn't yet built. I think I have a fix for it (which
was rather simple). I'll give the nitty-gritty details on 1064.
Julian Hyde wrote:
> Yes, that was pretty much the problem I saw. (I didn't clean
> everything out of .m2/repository, just the calcite and avatica stuff,
> so it should have been able to build offline.)
>
> FWIW, I don't see 1064 as a show-stopper for the Avatica release. If
> there's a way to make the release by building twice, we should do it.
>
> On Tue, Mar 8, 2016 at 9:02 AM, Josh Elser<jo...@gmail.com> wrote:
>> > This is the issue I was thinking of
>> > https://issues.apache.org/jira/browse/CALCITE-1064
>> >
>> > Seems to be causing me headaches with the maven-release-plugin.
>> >
>> >
>> > Josh Elser wrote:
>>> >>
>>> >> Wait a second... How do you expect any build with dependencies to be
>>> >> working if you're offline and have no artifacts in the local repository?
Re: Heads-up: Avatica now "disconnected" from root project
Posted by Julian Hyde <jh...@apache.org>.
Yes, that was pretty much the problem I saw. (I didn't clean
everything out of .m2/repository, just the calcite and avatica stuff,
so it should have been able to build offline.)
FWIW, I don't see 1064 as a show-stopper for the Avatica release. If
there's a way to make the release by building twice, we should do it.
On Tue, Mar 8, 2016 at 9:02 AM, Josh Elser <jo...@gmail.com> wrote:
> This is the issue I was thinking of
> https://issues.apache.org/jira/browse/CALCITE-1064
>
> Seems to be causing me headaches with the maven-release-plugin.
>
>
> Josh Elser wrote:
>>
>> Wait a second... How do you expect any build with dependencies to be
>> working if you're offline and have no artifacts in the local repository?
>> :)
>>
>> Josh Elser wrote:
>>>
>>> I did intentionally change the groupId, but I'm not stuck on it. I
>>> figured it would be nice to have a single groupId which contains all of
>>> Avatica.
>>>
>>> My guess is that the build issue for Avatica is the same one that
>>> Calcite suffers from (I didn't spend time trying to fix that) -- the
>>> issue where one of the plugins in the parent module tries to download
>>> all of the jars for the contained modules (we have a JIRA issue for that
>>> somewhere IIRC).
>>>
>>> Julian Hyde wrote:
>>>>
>>>> Did you intend to change the groupId from “org.apache.calcite” to
>>>> “org.apache.calcite.avatica”? If so, I will check in fixes to
>>>> calcite’s (non-avatica) pom.xml files. I’ll also remove conjars from
>>>> avatica's maven repo list.
>>>>
>>>> It seems that offline build of avatica doesn’t work too well,
>>>> especially if ~/.m2/repository is empty. Can you take a look at that?
>>>>
>>>> Julian
>>>>
>>>>> On Mar 7, 2016, at 3:24 PM, Josh Elser<jo...@gmail.com> wrote:
>>>>>
>>>>> Aww, beautiful. Thanks for making the time to do this. I completely
>>>>> punted on it, and am grateful that you picked it up now.
>>>>>
>>>>> Yes, consider this a formal volunteering for RM for Avatica. I'll try
>>>>> to get an RC spun up Tuesday or Wednesday.
>>>>>
>>>>> Julian Hyde wrote:
>>>>>>
>>>>>> I discovered a problem with the “ln -s” approach, and so abandoned
>>>>>> it: since there was only one Jekyll site, it is not possible to give
>>>>>> the Avatica site separate branding (logo, color scheme, and menu
>>>>>> structure).
>>>>>>
>>>>>> I now think the best approach is to have a separate Jekyll instance
>>>>>> (i.e. you should run “bundle exec jekyll serve” from avatica/site if
>>>>>> you are developing the avatica web site) but have both deploy to the
>>>>>> same calcite/site/target directory. See the updated README[1].
>>>>>>
>>>>>> I have created an Avatica logo and color scheme and deployed the
>>>>>> results to https://calcite.apache.org/avatica/. The web site is
>>>>>> incomplete, and I’d be the first to admit that the logo& color
>>>>>> scheme are not great, but something’s better than nothing. I don’t
>>>>>> think there are any links from https://calcite.apache.org/ to
>>>>>> https://calcite.apache.org/avatica so casual browsers will not
>>>>>> notice the work-in-progress.
>>>>>>
>>>>>>
>>>>>>> On Mar 7, 2016, at 11:21 AM, Josh Elser<jo...@gmail.com> wrote:
>>>>>>>
>>>>>>> Regarding the build: everything is working to the best of my
>>>>>>> knowledge.
>>>>>>
>>>>>> Great.
>>>>>>
>>>>>>> How do you (and others) feel about me throwing together a release
>>>>>>> candidate for an Avatica 1.7.0? I'm assuming we'll have to work in
>>>>>>> tandem the first time (first couple of times?) until we get a good
>>>>>>> process in place.
>>>>>>
>>>>>> I take it you’re volunteering to be release manager? Thanks! It
>>>>>> doesn’t seem too early for a first RC.
>>>>>>
>>>>>> Julian
>>>>>>
>>>>>> [1]
>>>>>>
>>>>>> https://github.com/apache/calcite/blob/master/avatica/site/README.md<https://github.com/apache/calcite/blob/master/avatica/site/README.md>
>>>>>>
>>>>>>
>>>>>> <https://github.com/apache/calcite/blob/master/avatica/site/README.md%3Chttps://github.com/apache/calcite/blob/master/avatica/site/README.md%3E>
>>>>>>
>>>>>>
>>>>
>
Re: Heads-up: Avatica now "disconnected" from root project
Posted by Josh Elser <jo...@gmail.com>.
This is the issue I was thinking of
https://issues.apache.org/jira/browse/CALCITE-1064
Seems to be causing me headaches with the maven-release-plugin.
Josh Elser wrote:
> Wait a second... How do you expect any build with dependencies to be
> working if you're offline and have no artifacts in the local repository? :)
>
> Josh Elser wrote:
>> I did intentionally change the groupId, but I'm not stuck on it. I
>> figured it would be nice to have a single groupId which contains all of
>> Avatica.
>>
>> My guess is that the build issue for Avatica is the same one that
>> Calcite suffers from (I didn't spend time trying to fix that) -- the
>> issue where one of the plugins in the parent module tries to download
>> all of the jars for the contained modules (we have a JIRA issue for that
>> somewhere IIRC).
>>
>> Julian Hyde wrote:
>>> Did you intend to change the groupId from “org.apache.calcite” to
>>> “org.apache.calcite.avatica”? If so, I will check in fixes to
>>> calcite’s (non-avatica) pom.xml files. I’ll also remove conjars from
>>> avatica's maven repo list.
>>>
>>> It seems that offline build of avatica doesn’t work too well,
>>> especially if ~/.m2/repository is empty. Can you take a look at that?
>>>
>>> Julian
>>>
>>>> On Mar 7, 2016, at 3:24 PM, Josh Elser<jo...@gmail.com> wrote:
>>>>
>>>> Aww, beautiful. Thanks for making the time to do this. I completely
>>>> punted on it, and am grateful that you picked it up now.
>>>>
>>>> Yes, consider this a formal volunteering for RM for Avatica. I'll try
>>>> to get an RC spun up Tuesday or Wednesday.
>>>>
>>>> Julian Hyde wrote:
>>>>> I discovered a problem with the “ln -s” approach, and so abandoned
>>>>> it: since there was only one Jekyll site, it is not possible to give
>>>>> the Avatica site separate branding (logo, color scheme, and menu
>>>>> structure).
>>>>>
>>>>> I now think the best approach is to have a separate Jekyll instance
>>>>> (i.e. you should run “bundle exec jekyll serve” from avatica/site if
>>>>> you are developing the avatica web site) but have both deploy to the
>>>>> same calcite/site/target directory. See the updated README[1].
>>>>>
>>>>> I have created an Avatica logo and color scheme and deployed the
>>>>> results to https://calcite.apache.org/avatica/. The web site is
>>>>> incomplete, and I’d be the first to admit that the logo& color
>>>>> scheme are not great, but something’s better than nothing. I don’t
>>>>> think there are any links from https://calcite.apache.org/ to
>>>>> https://calcite.apache.org/avatica so casual browsers will not
>>>>> notice the work-in-progress.
>>>>>
>>>>>
>>>>>> On Mar 7, 2016, at 11:21 AM, Josh Elser<jo...@gmail.com> wrote:
>>>>>>
>>>>>> Regarding the build: everything is working to the best of my
>>>>>> knowledge.
>>>>> Great.
>>>>>
>>>>>> How do you (and others) feel about me throwing together a release
>>>>>> candidate for an Avatica 1.7.0? I'm assuming we'll have to work in
>>>>>> tandem the first time (first couple of times?) until we get a good
>>>>>> process in place.
>>>>> I take it you’re volunteering to be release manager? Thanks! It
>>>>> doesn’t seem too early for a first RC.
>>>>>
>>>>> Julian
>>>>>
>>>>> [1]
>>>>> https://github.com/apache/calcite/blob/master/avatica/site/README.md<https://github.com/apache/calcite/blob/master/avatica/site/README.md>
>>>>>
>>>>> <https://github.com/apache/calcite/blob/master/avatica/site/README.md%3Chttps://github.com/apache/calcite/blob/master/avatica/site/README.md%3E>
>>>>>
>>>>>
>>>
Re: Heads-up: Avatica now "disconnected" from root project
Posted by Josh Elser <jo...@gmail.com>.
Wait a second... How do you expect any build with dependencies to be
working if you're offline and have no artifacts in the local repository? :)
Josh Elser wrote:
> I did intentionally change the groupId, but I'm not stuck on it. I
> figured it would be nice to have a single groupId which contains all of
> Avatica.
>
> My guess is that the build issue for Avatica is the same one that
> Calcite suffers from (I didn't spend time trying to fix that) -- the
> issue where one of the plugins in the parent module tries to download
> all of the jars for the contained modules (we have a JIRA issue for that
> somewhere IIRC).
>
> Julian Hyde wrote:
>> Did you intend to change the groupId from “org.apache.calcite” to
>> “org.apache.calcite.avatica”? If so, I will check in fixes to
>> calcite’s (non-avatica) pom.xml files. I’ll also remove conjars from
>> avatica's maven repo list.
>>
>> It seems that offline build of avatica doesn’t work too well,
>> especially if ~/.m2/repository is empty. Can you take a look at that?
>>
>> Julian
>>
>>> On Mar 7, 2016, at 3:24 PM, Josh Elser<jo...@gmail.com> wrote:
>>>
>>> Aww, beautiful. Thanks for making the time to do this. I completely
>>> punted on it, and am grateful that you picked it up now.
>>>
>>> Yes, consider this a formal volunteering for RM for Avatica. I'll try
>>> to get an RC spun up Tuesday or Wednesday.
>>>
>>> Julian Hyde wrote:
>>>> I discovered a problem with the “ln -s” approach, and so abandoned
>>>> it: since there was only one Jekyll site, it is not possible to give
>>>> the Avatica site separate branding (logo, color scheme, and menu
>>>> structure).
>>>>
>>>> I now think the best approach is to have a separate Jekyll instance
>>>> (i.e. you should run “bundle exec jekyll serve” from avatica/site if
>>>> you are developing the avatica web site) but have both deploy to the
>>>> same calcite/site/target directory. See the updated README[1].
>>>>
>>>> I have created an Avatica logo and color scheme and deployed the
>>>> results to https://calcite.apache.org/avatica/. The web site is
>>>> incomplete, and I’d be the first to admit that the logo& color
>>>> scheme are not great, but something’s better than nothing. I don’t
>>>> think there are any links from https://calcite.apache.org/ to
>>>> https://calcite.apache.org/avatica so casual browsers will not
>>>> notice the work-in-progress.
>>>>
>>>>
>>>>> On Mar 7, 2016, at 11:21 AM, Josh Elser<jo...@gmail.com> wrote:
>>>>>
>>>>> Regarding the build: everything is working to the best of my
>>>>> knowledge.
>>>> Great.
>>>>
>>>>> How do you (and others) feel about me throwing together a release
>>>>> candidate for an Avatica 1.7.0? I'm assuming we'll have to work in
>>>>> tandem the first time (first couple of times?) until we get a good
>>>>> process in place.
>>>> I take it you’re volunteering to be release manager? Thanks! It
>>>> doesn’t seem too early for a first RC.
>>>>
>>>> Julian
>>>>
>>>> [1]
>>>> https://github.com/apache/calcite/blob/master/avatica/site/README.md<https://github.com/apache/calcite/blob/master/avatica/site/README.md>
>>>> <https://github.com/apache/calcite/blob/master/avatica/site/README.md%3Chttps://github.com/apache/calcite/blob/master/avatica/site/README.md%3E>
>>>>
>>
Re: Heads-up: Avatica now "disconnected" from root project
Posted by Julian Hyde <jh...@apache.org>.
OK, let’s not rename to core. After we have removed the “calcite-“ prefix, the module in the “avatica” directory will be called “avatica-parent” and the module in the “avatica/core” directory will be called “avatica”.
Julian
> On Mar 8, 2016, at 12:16 PM, Josh Elser <jo...@gmail.com> wrote:
>
> +1 works for me.
>
> I'm undecided on avatica-core. Eventually, I think it should be split into an API and Client module, but, for now, I figured "core" is at least generic enough. I'm happy to entertain any other name suggestions.
>
> Julian Hyde wrote:
>> On Tue, Mar 8, 2016 at 7:00 AM, Josh Elser<jo...@gmail.com> wrote:
>>> I did intentionally change the groupId, but I'm not stuck on it. I figured
>>> it would be nice to have a single groupId which contains all of Avatica.
>>
>> Let's talk about maven module names. It will be difficult to change
>> them after the release.
>>
>> I like the idea of avatica modules having groupId "org.apache.calcite.avatica".
>>
>> Currently their names are prefixed "calcite-avatica-", e.g.
>> "calcite-avatica", "calcite-avatica-server",
>> "calcite-avatica-metrics-dropwizardmetrics3". "calcite-avatica-noop".
>> I think we should remove the "calcite-" prefix, hence "avatica",
>> "avatica-server", "avatica-metrics",
>> "avatica-metrics-dropwizardmetrics3", "avatica-noop". Each module
>> would still have "Apache Calcite" in its name, for example "Apache
>> Calcite Avatica Server", and of course in its groupId. What do you
>> think?
>>
>> Also, should we rename "avatica" to "avatica-core"? Less sure about that one.
>>
>> Julian
Re: Heads-up: Avatica now "disconnected" from root project
Posted by Josh Elser <jo...@gmail.com>.
+1 works for me.
I'm undecided on avatica-core. Eventually, I think it should be split
into an API and Client module, but, for now, I figured "core" is at
least generic enough. I'm happy to entertain any other name suggestions.
Julian Hyde wrote:
> On Tue, Mar 8, 2016 at 7:00 AM, Josh Elser<jo...@gmail.com> wrote:
>> I did intentionally change the groupId, but I'm not stuck on it. I figured
>> it would be nice to have a single groupId which contains all of Avatica.
>
> Let's talk about maven module names. It will be difficult to change
> them after the release.
>
> I like the idea of avatica modules having groupId "org.apache.calcite.avatica".
>
> Currently their names are prefixed "calcite-avatica-", e.g.
> "calcite-avatica", "calcite-avatica-server",
> "calcite-avatica-metrics-dropwizardmetrics3". "calcite-avatica-noop".
> I think we should remove the "calcite-" prefix, hence "avatica",
> "avatica-server", "avatica-metrics",
> "avatica-metrics-dropwizardmetrics3", "avatica-noop". Each module
> would still have "Apache Calcite" in its name, for example "Apache
> Calcite Avatica Server", and of course in its groupId. What do you
> think?
>
> Also, should we rename "avatica" to "avatica-core"? Less sure about that one.
>
> Julian
Re: Heads-up: Avatica now "disconnected" from root project
Posted by Julian Hyde <jh...@apache.org>.
On Tue, Mar 8, 2016 at 7:00 AM, Josh Elser <jo...@gmail.com> wrote:
> I did intentionally change the groupId, but I'm not stuck on it. I figured
> it would be nice to have a single groupId which contains all of Avatica.
Let's talk about maven module names. It will be difficult to change
them after the release.
I like the idea of avatica modules having groupId "org.apache.calcite.avatica".
Currently their names are prefixed "calcite-avatica-", e.g.
"calcite-avatica", "calcite-avatica-server",
"calcite-avatica-metrics-dropwizardmetrics3". "calcite-avatica-noop".
I think we should remove the "calcite-" prefix, hence "avatica",
"avatica-server", "avatica-metrics",
"avatica-metrics-dropwizardmetrics3", "avatica-noop". Each module
would still have "Apache Calcite" in its name, for example "Apache
Calcite Avatica Server", and of course in its groupId. What do you
think?
Also, should we rename "avatica" to "avatica-core"? Less sure about that one.
Julian
Re: Heads-up: Avatica now "disconnected" from root project
Posted by Josh Elser <jo...@gmail.com>.
I did intentionally change the groupId, but I'm not stuck on it. I
figured it would be nice to have a single groupId which contains all of
Avatica.
My guess is that the build issue for Avatica is the same one that
Calcite suffers from (I didn't spend time trying to fix that) -- the
issue where one of the plugins in the parent module tries to download
all of the jars for the contained modules (we have a JIRA issue for that
somewhere IIRC).
Julian Hyde wrote:
> Did you intend to change the groupId from “org.apache.calcite” to “org.apache.calcite.avatica”? If so, I will check in fixes to calcite’s (non-avatica) pom.xml files. I’ll also remove conjars from avatica's maven repo list.
>
> It seems that offline build of avatica doesn’t work too well, especially if ~/.m2/repository is empty. Can you take a look at that?
>
> Julian
>
>> On Mar 7, 2016, at 3:24 PM, Josh Elser<jo...@gmail.com> wrote:
>>
>> Aww, beautiful. Thanks for making the time to do this. I completely punted on it, and am grateful that you picked it up now.
>>
>> Yes, consider this a formal volunteering for RM for Avatica. I'll try to get an RC spun up Tuesday or Wednesday.
>>
>> Julian Hyde wrote:
>>> I discovered a problem with the “ln -s” approach, and so abandoned it: since there was only one Jekyll site, it is not possible to give the Avatica site separate branding (logo, color scheme, and menu structure).
>>>
>>> I now think the best approach is to have a separate Jekyll instance (i.e. you should run “bundle exec jekyll serve” from avatica/site if you are developing the avatica web site) but have both deploy to the same calcite/site/target directory. See the updated README[1].
>>>
>>> I have created an Avatica logo and color scheme and deployed the results to https://calcite.apache.org/avatica/. The web site is incomplete, and I’d be the first to admit that the logo& color scheme are not great, but something’s better than nothing. I don’t think there are any links from https://calcite.apache.org/ to https://calcite.apache.org/avatica so casual browsers will not notice the work-in-progress.
>>>
>>>
>>>> On Mar 7, 2016, at 11:21 AM, Josh Elser<jo...@gmail.com> wrote:
>>>>
>>>> Regarding the build: everything is working to the best of my knowledge.
>>> Great.
>>>
>>>> How do you (and others) feel about me throwing together a release candidate for an Avatica 1.7.0? I'm assuming we'll have to work in tandem the first time (first couple of times?) until we get a good process in place.
>>> I take it you’re volunteering to be release manager? Thanks! It doesn’t seem too early for a first RC.
>>>
>>> Julian
>>>
>>> [1] https://github.com/apache/calcite/blob/master/avatica/site/README.md<https://github.com/apache/calcite/blob/master/avatica/site/README.md> <https://github.com/apache/calcite/blob/master/avatica/site/README.md%3Chttps://github.com/apache/calcite/blob/master/avatica/site/README.md%3E>
>
Re: Heads-up: Avatica now "disconnected" from root project
Posted by Julian Hyde <jh...@apache.org>.
Did you intend to change the groupId from “org.apache.calcite” to “org.apache.calcite.avatica”? If so, I will check in fixes to calcite’s (non-avatica) pom.xml files. I’ll also remove conjars from avatica's maven repo list.
It seems that offline build of avatica doesn’t work too well, especially if ~/.m2/repository is empty. Can you take a look at that?
Julian
> On Mar 7, 2016, at 3:24 PM, Josh Elser <jo...@gmail.com> wrote:
>
> Aww, beautiful. Thanks for making the time to do this. I completely punted on it, and am grateful that you picked it up now.
>
> Yes, consider this a formal volunteering for RM for Avatica. I'll try to get an RC spun up Tuesday or Wednesday.
>
> Julian Hyde wrote:
>> I discovered a problem with the “ln -s” approach, and so abandoned it: since there was only one Jekyll site, it is not possible to give the Avatica site separate branding (logo, color scheme, and menu structure).
>>
>> I now think the best approach is to have a separate Jekyll instance (i.e. you should run “bundle exec jekyll serve” from avatica/site if you are developing the avatica web site) but have both deploy to the same calcite/site/target directory. See the updated README[1].
>>
>> I have created an Avatica logo and color scheme and deployed the results to https://calcite.apache.org/avatica/. The web site is incomplete, and I’d be the first to admit that the logo& color scheme are not great, but something’s better than nothing. I don’t think there are any links from https://calcite.apache.org/ to https://calcite.apache.org/avatica so casual browsers will not notice the work-in-progress.
>>
>>
>>> On Mar 7, 2016, at 11:21 AM, Josh Elser<jo...@gmail.com> wrote:
>>>
>>> Regarding the build: everything is working to the best of my knowledge.
>>
>> Great.
>>
>>> How do you (and others) feel about me throwing together a release candidate for an Avatica 1.7.0? I'm assuming we'll have to work in tandem the first time (first couple of times?) until we get a good process in place.
>>
>> I take it you’re volunteering to be release manager? Thanks! It doesn’t seem too early for a first RC.
>>
>> Julian
>>
>> [1] https://github.com/apache/calcite/blob/master/avatica/site/README.md<https://github.com/apache/calcite/blob/master/avatica/site/README.md> <https://github.com/apache/calcite/blob/master/avatica/site/README.md%3Chttps://github.com/apache/calcite/blob/master/avatica/site/README.md%3E>
Re: Heads-up: Avatica now "disconnected" from root project
Posted by Josh Elser <jo...@gmail.com>.
Aww, beautiful. Thanks for making the time to do this. I completely
punted on it, and am grateful that you picked it up now.
Yes, consider this a formal volunteering for RM for Avatica. I'll try to
get an RC spun up Tuesday or Wednesday.
Julian Hyde wrote:
> I discovered a problem with the “ln -s” approach, and so abandoned it: since there was only one Jekyll site, it is not possible to give the Avatica site separate branding (logo, color scheme, and menu structure).
>
> I now think the best approach is to have a separate Jekyll instance (i.e. you should run “bundle exec jekyll serve” from avatica/site if you are developing the avatica web site) but have both deploy to the same calcite/site/target directory. See the updated README[1].
>
> I have created an Avatica logo and color scheme and deployed the results to https://calcite.apache.org/avatica/. The web site is incomplete, and I’d be the first to admit that the logo& color scheme are not great, but something’s better than nothing. I don’t think there are any links from https://calcite.apache.org/ to https://calcite.apache.org/avatica so casual browsers will not notice the work-in-progress.
>
>
>> On Mar 7, 2016, at 11:21 AM, Josh Elser<jo...@gmail.com> wrote:
>>
>> Regarding the build: everything is working to the best of my knowledge.
>
> Great.
>
>> How do you (and others) feel about me throwing together a release candidate for an Avatica 1.7.0? I'm assuming we'll have to work in tandem the first time (first couple of times?) until we get a good process in place.
>
> I take it you’re volunteering to be release manager? Thanks! It doesn’t seem too early for a first RC.
>
> Julian
>
> [1] https://github.com/apache/calcite/blob/master/avatica/site/README.md<https://github.com/apache/calcite/blob/master/avatica/site/README.md>
>
>
Re: Heads-up: Avatica now "disconnected" from root project
Posted by Julian Hyde <jh...@apache.org>.
I discovered a problem with the “ln -s” approach, and so abandoned it: since there was only one Jekyll site, it is not possible to give the Avatica site separate branding (logo, color scheme, and menu structure).
I now think the best approach is to have a separate Jekyll instance (i.e. you should run “bundle exec jekyll serve” from avatica/site if you are developing the avatica web site) but have both deploy to the same calcite/site/target directory. See the updated README[1].
I have created an Avatica logo and color scheme and deployed the results to https://calcite.apache.org/avatica/. The web site is incomplete, and I’d be the first to admit that the logo & color scheme are not great, but something’s better than nothing. I don’t think there are any links from https://calcite.apache.org/ to https://calcite.apache.org/avatica so casual browsers will not notice the work-in-progress.
> On Mar 7, 2016, at 11:21 AM, Josh Elser <jo...@gmail.com> wrote:
>
> Regarding the build: everything is working to the best of my knowledge.
Great.
> How do you (and others) feel about me throwing together a release candidate for an Avatica 1.7.0? I'm assuming we'll have to work in tandem the first time (first couple of times?) until we get a good process in place.
I take it you’re volunteering to be release manager? Thanks! It doesn’t seem too early for a first RC.
Julian
[1] https://github.com/apache/calcite/blob/master/avatica/site/README.md <https://github.com/apache/calcite/blob/master/avatica/site/README.md>
Re: Heads-up: Avatica now "disconnected" from root project
Posted by Josh Elser <jo...@gmail.com>.
Oh that's easy! I had just copied the generated site for Avatica (jekyll
build) into the target for the Calcite site after it built initially.
Long term -- yes, it'd be good to separate the two, but I kept them
more-or-less the same just to not block us on that redesign.
Regarding the build: everything is working to the best of my knowledge.
How do you (and others) feel about me throwing together a release
candidate for an Avatica 1.7.0? I'm assuming we'll have to work in
tandem the first time (first couple of times?) until we get a good
process in place.
If you want to throw together an Avatica specific logo, that'd be awesome :)
Julian Hyde wrote:
> 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<jh...@apache.org> 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<jo...@gmail.com> 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)<ji...@apache.org>
>>> Reply-To: dev@calcite.apache.org
>>> To: issues@calcite.apache.org
>>>
>>>
>>> [ 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)
>
>
Re: Heads-up: Avatica now "disconnected" from root project
Posted by Julian Hyde <jh...@apache.org>.
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 <jh...@apache.org> 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 <jo...@gmail.com> 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) <ji...@apache.org>
>> Reply-To: dev@calcite.apache.org
>> To: issues@calcite.apache.org
>>
>>
>> [ 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)
>