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 <[email protected]> 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<[email protected]> 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<[email protected]> 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> >>>>>> >>>>>> >>>> >
