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<[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?
