incubator-bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Foley <mfo...@hortonworks.com>
Subject Re: iTest.next
Date Mon, 07 Nov 2011 21:24:44 GMT
Looking at Gradle, I found this disconcerting statement (
http://stackoverflow.com/questions/1163173/why-use-gradle-instead-of-ant-or-maven):

> Groovy is much nicer to code than XML.


Are you proposing that we manage the build system in Groovy?
Unless the whole ecosystem can be moved in this direction, I would
recommend against it.

--Matt

On Mon, Nov 7, 2011 at 11:57 AM, Tom White <tom@cloudera.com> wrote:

> +1 to lowering the barrier to entry for contributing new tests (#7).
>
> Also, rather than introduce a new build system, why not improve the
> plugin (failsafe) if it has deficiencies?
>
> Tom
>
> On Fri, Nov 4, 2011 at 4:00 PM, Roman Shaposhnik <rvs@apache.org> wrote:
> > Folks,
> >
> > one of the biggest challenges that I'd like to tackle post Bigtop
> > 0.2.0 is increasing
> > the scope, coverage and robustness of the iTest and its test artifacts.
> To that
> > end I've started a Wiki page outlining the issues:
> >    https://cwiki.apache.org/confluence/display/BIGTOP/iTest.next
> >
> > Feel free to contribute and I really hope we can spend some time at
> ApacheCON
> > talking about that.
> >
> > Thanks,
> > Roman.
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message