The Apache Jenkins build system has built Calcite-Master (build #173)
Status: Still Failing
Check console output at https://builds.apache.org/job/Calcite-Master/173/ to
view the results.
We already have a tool that provides a container for the whole build process.
That tool is maven. I do not recall a time where someone had problems because
they had the wrong version of maven installed; so this is a non-problem.
I’ve written C/C++ projects before (using autoconf, libtool, mingw
Yes.
But I claim that adding mvnw to the picture makes things more complicated for
the typical user, because there are now more options to understand.
Julian
> On Jan 2, 2018, at 2:00 PM, Michael Mior wrote:
>
> Even if we do include mvnw, isn't it still possible to use a
Even if we do include mvnw, isn't it still possible to use a compatible mvn
directly?
--
Michael Mior
mm...@apache.org
2018-01-02 15:35 GMT-05:00 Julian Hyde :
> True, but for 2 and 3 it’s not much of a hardship to type
>
> $ /usr/local/maven-x.y.z/bin/mvn -s my-settings.xml
True, but for 2 and 3 it’s not much of a hardship to type
$ /usr/local/maven-x.y.z/bin/mvn -s my-settings.xml target
rather than
$ mvn target
And for 1, I claim that typing “mvn” is less surprising to most people than
typing “mvnw”. Because most people who build java code these days are
>Multiple versions of Maven can be installed side-by-side (and we don't
have esoteric requirements). As such, I don't see the need for such a
change
The reasons could include:
1) Simplified Apache Maven installation for those who have no experience
with it
2) Having multiple settings.xml files
Good point! The last Avatica release aged out of those populated by the
reporting tool but I think it makes sense to include the latest Avatica
release as well.
--
Michael Mior
mm...@apache.org
2018-01-02 14:36 GMT-05:00 Josh Elser :
> +1
>
> Maybe include the last Avatica
+1
Maybe include the last Avatica release too? (1.10.0 on 2017/05/29)
On 12/31/17 5:39 PM, Michael Mior wrote:
See below a draft of the board report for Jan. 17. I borrowed heavily from
past reports and the release notes but I think the necessary points are
covered. If there's any activity I'm
Well put, all. I think I would be -1 on such a change without
better/specific reasons as to what is broken/bad.
Multiple versions of Maven can be installed side-by-side (and we don't
have esoteric requirements). As such, I don't see the need for such a
change.
On 12/31/17 2:27 AM, Julian