Adding Gradle to Zeppelin

[Anthony Corbacho <an...@apache.org>]

Hi,

Few month back, I started to work on integrating Gradle to zeppelin (pull
request: pull/171 <https://github.com/NFLabs/zeppelin/pull/171>) But I
didnt had the time to finish and complete it :(
So the question here is more like, Should we keep on and try to switch from
mvn to gradle?
What do you think guys?

Anthony

Re: Adding Gradle to Zeppelin

[Anthony Corbacho <an...@apache.org>]

List of things that should be include in this PR:


   - compile, build, unit test
   - creating distribution package
   - running integration test
   - force dependency library version
   - deploy artifact to maven central


On Mon, Jan 12, 2015 at 5:50 PM, Kevin Kim (Sangwoo) <ke...@between.us>
wrote:

> +1 for gradle,
> I like it much than maven, too.
> On Mon Jan 12 2015 at 5:13:17 PM Anthony Corbacho <
> anthonycorbacho@apache.org> wrote:
>
> > If we can come up with a list of things that we need, I can add them.
> >
> > On Mon, Jan 12, 2015 at 5:02 PM, moon soo Lee <mo...@apache.org> wrote:
> >
> > > +1
> > >
> > > it's been very long to have that PR open. I guess it is not that simple
> > job
> > > to make all behavior working just as current mvn.
> > > If it takes too long, i think we can discuss minimum requirement of
> > gradle
> > > build. With quick minimum build support pushed to source tree, maybe we
> > can
> > > attract people who prefer use gradle and can get chances of feedback
> and
> > > improvements.
> > >
> > > Best,
> > > moon
> > >
> > > 2015년 1월 12일 월요일, Alex B.<bz...@apache.org>님이 작성한 메시지:
> > >
> > > > Same here, enthusiastic +1 for gradle
> > > >
> > > > After years of mvn I would rather prefer gradle now, although better
> to
> > > > exercise caution here as having a full featured programming language
> in
> > > > build file may make things unnecessary complicated too.
> > > >
> > > > On Mon, Jan 12, 2015 at 4:40 PM, Roman Shaposhnik <
> > roman@shaposhnik.org
> > > > <javascript:;>>
> > > > wrote:
> > > >
> > > > > On Sun, Jan 11, 2015 at 11:34 PM, Anthony Corbacho
> > > > > <anthonycorbacho@apache.org <javascript:;>> wrote:
> > > > > > Hi,
> > > > > >
> > > > > > Few month back, I started to work on integrating Gradle to
> zeppelin
> > > > (pull
> > > > > > request: pull/171 <https://github.com/NFLabs/zeppelin/pull/171>)
> > > But I
> > > > > > didnt had the time to finish and complete it :(
> > > > > > So the question here is more like, Should we keep on and try to
> > > switch
> > > > > from
> > > > > > mvn to gradle?
> > > > > > What do you think guys?
> > > > >
> > > > > FWIW: I'm a huge fan of gradle. Not sure if I can promise
> > > > > to commit coding cycles, but at least I can share my experiences
> > > > > via answering questions, etc.
> > > > >
> > > > > Thanks,
> > > > > Roman.
> > > > >
> > > >
> > >
> >
>

Re: Adding Gradle to Zeppelin

[moon soo Lee <mo...@apache.org>]

And if i add something on Anthony's list,

 - build based on profile set (equivalent to mvn -P)
 - overriding dependency's version (equivalent to mvn -D)
 - run checkstyle plugin

Best,
moon

On Mon, Jan 12, 2015 at 7:43 PM, moon soo Lee <mo...@apache.org> wrote:

> about SBT
>
> Currently Zeppelin have strong integration with Apache Spark. Apache Spark
> is the one who written in scala and they uses sbt (and maven) for their
> build system. In this manner, supporting sbt sounds reasonable. However in
> the future, I think Zeppelin would like to support more backends, it'll not
> be only scala based one but also other languages, too. So I think build
> system doesn't need to be specialized for scala.
>
> Also having more than 2 build system doesn't make sense to me, too.
> if we want to add one advanced build system, +1 for gradle.
>
>
> On Mon, Jan 12, 2015 at 7:11 PM, Kevin Kim (Sangwoo) <ke...@between.us>
> wrote:
>
>> Agreed with Alex, too.
>> On Mon Jan 12 2015 at 7:07:11 PM Anthony Corbacho <
>> anthonycorbacho@apache.org> wrote:
>>
>> > I agree with Alex.
>> >
>> > On Mon, Jan 12, 2015 at 7:02 PM, Alex B. <bz...@apache.org> wrote:
>> >
>> > > At least for me, SBT is the least preferable choice.
>> > >
>> > > I like grade because of it polyglot nature: so we can build Java,
>> Scala,
>> > > C++ with all the same build system. This adds enough flexibility for
>> the
>> > > future of the project.
>> > > Nice bonus is the way of version conflict of the transitive
>> dependences
>> > are
>> > > handled there, which is a very common case in Hadoop ecosystem.
>> > >
>> > > Supporting Maven is OK with me as soon as it works, but.. you are
>> right,
>> > > better not support 2 build systems, so if moving - only a Gradle makes
>> > > sense to me.
>> > >
>> > >
>> > > On Mon, Jan 12, 2015 at 6:49 PM, Eric Charles <er...@apache.org>
>> wrote:
>> > >
>> > > > -1
>> > > >
>> > > > IMHO Maven is good enough for what it needs now.
>> > > > SBT would be another option and a more natural fit, especially if we
>> > > > plan to add more "scala-like" frameworks in the future (Play...).
>> > > >
>> > > > Anyway, would it make sense that I jump as maintainer of maven
>> pom(s),
>> > > > adding SBT in the future?
>> > > > Having two build systems is not ideal, but can help some guys and
>> have
>> > a
>> > > > broader coverage.
>> > > >
>> > > > Thx, Eric
>> > > >
>> > > >
>> > > > On 01/12/2015 09:50 AM, Kevin Kim (Sangwoo) wrote:
>> > > > > +1 for gradle,
>> > > > > I like it much than maven, too.
>> > > > > On Mon Jan 12 2015 at 5:13:17 PM Anthony Corbacho <
>> > > > > anthonycorbacho@apache.org> wrote:
>> > > > >
>> > > > >> If we can come up with a list of things that we need, I can add
>> > them.
>> > > > >>
>> > > > >> On Mon, Jan 12, 2015 at 5:02 PM, moon soo Lee <mo...@apache.org>
>> > > wrote:
>> > > > >>
>> > > > >>> +1
>> > > > >>>
>> > > > >>> it's been very long to have that PR open. I guess it is not that
>> > > simple
>> > > > >> job
>> > > > >>> to make all behavior working just as current mvn.
>> > > > >>> If it takes too long, i think we can discuss minimum
>> requirement of
>> > > > >> gradle
>> > > > >>> build. With quick minimum build support pushed to source tree,
>> > maybe
>> > > we
>> > > > >> can
>> > > > >>> attract people who prefer use gradle and can get chances of
>> > feedback
>> > > > and
>> > > > >>> improvements.
>> > > > >>>
>> > > > >>> Best,
>> > > > >>> moon
>> > > > >>>
>> > > > >>> 2015년 1월 12일 월요일, Alex B.<bz...@apache.org>님이 작성한 메시지:
>> > > > >>>
>> > > > >>>> Same here, enthusiastic +1 for gradle
>> > > > >>>>
>> > > > >>>> After years of mvn I would rather prefer gradle now, although
>> > better
>> > > > to
>> > > > >>>> exercise caution here as having a full featured programming
>> > language
>> > > > in
>> > > > >>>> build file may make things unnecessary complicated too.
>> > > > >>>>
>> > > > >>>> On Mon, Jan 12, 2015 at 4:40 PM, Roman Shaposhnik <
>> > > > >> roman@shaposhnik.org
>> > > > >>>> <javascript:;>>
>> > > > >>>> wrote:
>> > > > >>>>
>> > > > >>>>> On Sun, Jan 11, 2015 at 11:34 PM, Anthony Corbacho
>> > > > >>>>> <anthonycorbacho@apache.org <javascript:;>> wrote:
>> > > > >>>>>> Hi,
>> > > > >>>>>>
>> > > > >>>>>> Few month back, I started to work on integrating Gradle to
>> > > zeppelin
>> > > > >>>> (pull
>> > > > >>>>>> request: pull/171 <
>> https://github.com/NFLabs/zeppelin/pull/171
>> > >)
>> > > > >>> But I
>> > > > >>>>>> didnt had the time to finish and complete it :(
>> > > > >>>>>> So the question here is more like, Should we keep on and try
>> to
>> > > > >>> switch
>> > > > >>>>> from
>> > > > >>>>>> mvn to gradle?
>> > > > >>>>>> What do you think guys?
>> > > > >>>>> FWIW: I'm a huge fan of gradle. Not sure if I can promise
>> > > > >>>>> to commit coding cycles, but at least I can share my
>> experiences
>> > > > >>>>> via answering questions, etc.
>> > > > >>>>>
>> > > > >>>>> Thanks,
>> > > > >>>>> Roman.
>> > > > >>>>>
>> > > >
>> > >
>> >
>>
>
>

Re: Adding Gradle to Zeppelin

[moon soo Lee <mo...@apache.org>]

about SBT

Currently Zeppelin have strong integration with Apache Spark. Apache Spark
is the one who written in scala and they uses sbt (and maven) for their
build system. In this manner, supporting sbt sounds reasonable. However in
the future, I think Zeppelin would like to support more backends, it'll not
be only scala based one but also other languages, too. So I think build
system doesn't need to be specialized for scala.

Also having more than 2 build system doesn't make sense to me, too.
if we want to add one advanced build system, +1 for gradle.


On Mon, Jan 12, 2015 at 7:11 PM, Kevin Kim (Sangwoo) <ke...@between.us>
wrote:

> Agreed with Alex, too.
> On Mon Jan 12 2015 at 7:07:11 PM Anthony Corbacho <
> anthonycorbacho@apache.org> wrote:
>
> > I agree with Alex.
> >
> > On Mon, Jan 12, 2015 at 7:02 PM, Alex B. <bz...@apache.org> wrote:
> >
> > > At least for me, SBT is the least preferable choice.
> > >
> > > I like grade because of it polyglot nature: so we can build Java,
> Scala,
> > > C++ with all the same build system. This adds enough flexibility for
> the
> > > future of the project.
> > > Nice bonus is the way of version conflict of the transitive dependences
> > are
> > > handled there, which is a very common case in Hadoop ecosystem.
> > >
> > > Supporting Maven is OK with me as soon as it works, but.. you are
> right,
> > > better not support 2 build systems, so if moving - only a Gradle makes
> > > sense to me.
> > >
> > >
> > > On Mon, Jan 12, 2015 at 6:49 PM, Eric Charles <er...@apache.org> wrote:
> > >
> > > > -1
> > > >
> > > > IMHO Maven is good enough for what it needs now.
> > > > SBT would be another option and a more natural fit, especially if we
> > > > plan to add more "scala-like" frameworks in the future (Play...).
> > > >
> > > > Anyway, would it make sense that I jump as maintainer of maven
> pom(s),
> > > > adding SBT in the future?
> > > > Having two build systems is not ideal, but can help some guys and
> have
> > a
> > > > broader coverage.
> > > >
> > > > Thx, Eric
> > > >
> > > >
> > > > On 01/12/2015 09:50 AM, Kevin Kim (Sangwoo) wrote:
> > > > > +1 for gradle,
> > > > > I like it much than maven, too.
> > > > > On Mon Jan 12 2015 at 5:13:17 PM Anthony Corbacho <
> > > > > anthonycorbacho@apache.org> wrote:
> > > > >
> > > > >> If we can come up with a list of things that we need, I can add
> > them.
> > > > >>
> > > > >> On Mon, Jan 12, 2015 at 5:02 PM, moon soo Lee <mo...@apache.org>
> > > wrote:
> > > > >>
> > > > >>> +1
> > > > >>>
> > > > >>> it's been very long to have that PR open. I guess it is not that
> > > simple
> > > > >> job
> > > > >>> to make all behavior working just as current mvn.
> > > > >>> If it takes too long, i think we can discuss minimum requirement
> of
> > > > >> gradle
> > > > >>> build. With quick minimum build support pushed to source tree,
> > maybe
> > > we
> > > > >> can
> > > > >>> attract people who prefer use gradle and can get chances of
> > feedback
> > > > and
> > > > >>> improvements.
> > > > >>>
> > > > >>> Best,
> > > > >>> moon
> > > > >>>
> > > > >>> 2015년 1월 12일 월요일, Alex B.<bz...@apache.org>님이 작성한 메시지:
> > > > >>>
> > > > >>>> Same here, enthusiastic +1 for gradle
> > > > >>>>
> > > > >>>> After years of mvn I would rather prefer gradle now, although
> > better
> > > > to
> > > > >>>> exercise caution here as having a full featured programming
> > language
> > > > in
> > > > >>>> build file may make things unnecessary complicated too.
> > > > >>>>
> > > > >>>> On Mon, Jan 12, 2015 at 4:40 PM, Roman Shaposhnik <
> > > > >> roman@shaposhnik.org
> > > > >>>> <javascript:;>>
> > > > >>>> wrote:
> > > > >>>>
> > > > >>>>> On Sun, Jan 11, 2015 at 11:34 PM, Anthony Corbacho
> > > > >>>>> <anthonycorbacho@apache.org <javascript:;>> wrote:
> > > > >>>>>> Hi,
> > > > >>>>>>
> > > > >>>>>> Few month back, I started to work on integrating Gradle to
> > > zeppelin
> > > > >>>> (pull
> > > > >>>>>> request: pull/171 <
> https://github.com/NFLabs/zeppelin/pull/171
> > >)
> > > > >>> But I
> > > > >>>>>> didnt had the time to finish and complete it :(
> > > > >>>>>> So the question here is more like, Should we keep on and try
> to
> > > > >>> switch
> > > > >>>>> from
> > > > >>>>>> mvn to gradle?
> > > > >>>>>> What do you think guys?
> > > > >>>>> FWIW: I'm a huge fan of gradle. Not sure if I can promise
> > > > >>>>> to commit coding cycles, but at least I can share my
> experiences
> > > > >>>>> via answering questions, etc.
> > > > >>>>>
> > > > >>>>> Thanks,
> > > > >>>>> Roman.
> > > > >>>>>
> > > >
> > >
> >
>

Re: Adding Gradle to Zeppelin

["Kevin Kim (Sangwoo)" <ke...@between.us>]

Agreed with Alex, too.
On Mon Jan 12 2015 at 7:07:11 PM Anthony Corbacho <
anthonycorbacho@apache.org> wrote:

> I agree with Alex.
>
> On Mon, Jan 12, 2015 at 7:02 PM, Alex B. <bz...@apache.org> wrote:
>
> > At least for me, SBT is the least preferable choice.
> >
> > I like grade because of it polyglot nature: so we can build Java, Scala,
> > C++ with all the same build system. This adds enough flexibility for the
> > future of the project.
> > Nice bonus is the way of version conflict of the transitive dependences
> are
> > handled there, which is a very common case in Hadoop ecosystem.
> >
> > Supporting Maven is OK with me as soon as it works, but.. you are right,
> > better not support 2 build systems, so if moving - only a Gradle makes
> > sense to me.
> >
> >
> > On Mon, Jan 12, 2015 at 6:49 PM, Eric Charles <er...@apache.org> wrote:
> >
> > > -1
> > >
> > > IMHO Maven is good enough for what it needs now.
> > > SBT would be another option and a more natural fit, especially if we
> > > plan to add more "scala-like" frameworks in the future (Play...).
> > >
> > > Anyway, would it make sense that I jump as maintainer of maven pom(s),
> > > adding SBT in the future?
> > > Having two build systems is not ideal, but can help some guys and have
> a
> > > broader coverage.
> > >
> > > Thx, Eric
> > >
> > >
> > > On 01/12/2015 09:50 AM, Kevin Kim (Sangwoo) wrote:
> > > > +1 for gradle,
> > > > I like it much than maven, too.
> > > > On Mon Jan 12 2015 at 5:13:17 PM Anthony Corbacho <
> > > > anthonycorbacho@apache.org> wrote:
> > > >
> > > >> If we can come up with a list of things that we need, I can add
> them.
> > > >>
> > > >> On Mon, Jan 12, 2015 at 5:02 PM, moon soo Lee <mo...@apache.org>
> > wrote:
> > > >>
> > > >>> +1
> > > >>>
> > > >>> it's been very long to have that PR open. I guess it is not that
> > simple
> > > >> job
> > > >>> to make all behavior working just as current mvn.
> > > >>> If it takes too long, i think we can discuss minimum requirement of
> > > >> gradle
> > > >>> build. With quick minimum build support pushed to source tree,
> maybe
> > we
> > > >> can
> > > >>> attract people who prefer use gradle and can get chances of
> feedback
> > > and
> > > >>> improvements.
> > > >>>
> > > >>> Best,
> > > >>> moon
> > > >>>
> > > >>> 2015년 1월 12일 월요일, Alex B.<bz...@apache.org>님이 작성한 메시지:
> > > >>>
> > > >>>> Same here, enthusiastic +1 for gradle
> > > >>>>
> > > >>>> After years of mvn I would rather prefer gradle now, although
> better
> > > to
> > > >>>> exercise caution here as having a full featured programming
> language
> > > in
> > > >>>> build file may make things unnecessary complicated too.
> > > >>>>
> > > >>>> On Mon, Jan 12, 2015 at 4:40 PM, Roman Shaposhnik <
> > > >> roman@shaposhnik.org
> > > >>>> <javascript:;>>
> > > >>>> wrote:
> > > >>>>
> > > >>>>> On Sun, Jan 11, 2015 at 11:34 PM, Anthony Corbacho
> > > >>>>> <anthonycorbacho@apache.org <javascript:;>> wrote:
> > > >>>>>> Hi,
> > > >>>>>>
> > > >>>>>> Few month back, I started to work on integrating Gradle to
> > zeppelin
> > > >>>> (pull
> > > >>>>>> request: pull/171 <https://github.com/NFLabs/zeppelin/pull/171
> >)
> > > >>> But I
> > > >>>>>> didnt had the time to finish and complete it :(
> > > >>>>>> So the question here is more like, Should we keep on and try to
> > > >>> switch
> > > >>>>> from
> > > >>>>>> mvn to gradle?
> > > >>>>>> What do you think guys?
> > > >>>>> FWIW: I'm a huge fan of gradle. Not sure if I can promise
> > > >>>>> to commit coding cycles, but at least I can share my experiences
> > > >>>>> via answering questions, etc.
> > > >>>>>
> > > >>>>> Thanks,
> > > >>>>> Roman.
> > > >>>>>
> > >
> >
>

Re: Adding Gradle to Zeppelin

[Anthony Corbacho <an...@apache.org>]

I agree with Alex.

On Mon, Jan 12, 2015 at 7:02 PM, Alex B. <bz...@apache.org> wrote:

> At least for me, SBT is the least preferable choice.
>
> I like grade because of it polyglot nature: so we can build Java, Scala,
> C++ with all the same build system. This adds enough flexibility for the
> future of the project.
> Nice bonus is the way of version conflict of the transitive dependences are
> handled there, which is a very common case in Hadoop ecosystem.
>
> Supporting Maven is OK with me as soon as it works, but.. you are right,
> better not support 2 build systems, so if moving - only a Gradle makes
> sense to me.
>
>
> On Mon, Jan 12, 2015 at 6:49 PM, Eric Charles <er...@apache.org> wrote:
>
> > -1
> >
> > IMHO Maven is good enough for what it needs now.
> > SBT would be another option and a more natural fit, especially if we
> > plan to add more "scala-like" frameworks in the future (Play...).
> >
> > Anyway, would it make sense that I jump as maintainer of maven pom(s),
> > adding SBT in the future?
> > Having two build systems is not ideal, but can help some guys and have a
> > broader coverage.
> >
> > Thx, Eric
> >
> >
> > On 01/12/2015 09:50 AM, Kevin Kim (Sangwoo) wrote:
> > > +1 for gradle,
> > > I like it much than maven, too.
> > > On Mon Jan 12 2015 at 5:13:17 PM Anthony Corbacho <
> > > anthonycorbacho@apache.org> wrote:
> > >
> > >> If we can come up with a list of things that we need, I can add them.
> > >>
> > >> On Mon, Jan 12, 2015 at 5:02 PM, moon soo Lee <mo...@apache.org>
> wrote:
> > >>
> > >>> +1
> > >>>
> > >>> it's been very long to have that PR open. I guess it is not that
> simple
> > >> job
> > >>> to make all behavior working just as current mvn.
> > >>> If it takes too long, i think we can discuss minimum requirement of
> > >> gradle
> > >>> build. With quick minimum build support pushed to source tree, maybe
> we
> > >> can
> > >>> attract people who prefer use gradle and can get chances of feedback
> > and
> > >>> improvements.
> > >>>
> > >>> Best,
> > >>> moon
> > >>>
> > >>> 2015년 1월 12일 월요일, Alex B.<bz...@apache.org>님이 작성한 메시지:
> > >>>
> > >>>> Same here, enthusiastic +1 for gradle
> > >>>>
> > >>>> After years of mvn I would rather prefer gradle now, although better
> > to
> > >>>> exercise caution here as having a full featured programming language
> > in
> > >>>> build file may make things unnecessary complicated too.
> > >>>>
> > >>>> On Mon, Jan 12, 2015 at 4:40 PM, Roman Shaposhnik <
> > >> roman@shaposhnik.org
> > >>>> <javascript:;>>
> > >>>> wrote:
> > >>>>
> > >>>>> On Sun, Jan 11, 2015 at 11:34 PM, Anthony Corbacho
> > >>>>> <anthonycorbacho@apache.org <javascript:;>> wrote:
> > >>>>>> Hi,
> > >>>>>>
> > >>>>>> Few month back, I started to work on integrating Gradle to
> zeppelin
> > >>>> (pull
> > >>>>>> request: pull/171 <https://github.com/NFLabs/zeppelin/pull/171>)
> > >>> But I
> > >>>>>> didnt had the time to finish and complete it :(
> > >>>>>> So the question here is more like, Should we keep on and try to
> > >>> switch
> > >>>>> from
> > >>>>>> mvn to gradle?
> > >>>>>> What do you think guys?
> > >>>>> FWIW: I'm a huge fan of gradle. Not sure if I can promise
> > >>>>> to commit coding cycles, but at least I can share my experiences
> > >>>>> via answering questions, etc.
> > >>>>>
> > >>>>> Thanks,
> > >>>>> Roman.
> > >>>>>
> >
>

Re: Adding Gradle to Zeppelin

["Alex B." <bz...@apache.org>]

At least for me, SBT is the least preferable choice.

I like grade because of it polyglot nature: so we can build Java, Scala,
C++ with all the same build system. This adds enough flexibility for the
future of the project.
Nice bonus is the way of version conflict of the transitive dependences are
handled there, which is a very common case in Hadoop ecosystem.

Supporting Maven is OK with me as soon as it works, but.. you are right,
better not support 2 build systems, so if moving - only a Gradle makes
sense to me.


On Mon, Jan 12, 2015 at 6:49 PM, Eric Charles <er...@apache.org> wrote:

> -1
>
> IMHO Maven is good enough for what it needs now.
> SBT would be another option and a more natural fit, especially if we
> plan to add more "scala-like" frameworks in the future (Play...).
>
> Anyway, would it make sense that I jump as maintainer of maven pom(s),
> adding SBT in the future?
> Having two build systems is not ideal, but can help some guys and have a
> broader coverage.
>
> Thx, Eric
>
>
> On 01/12/2015 09:50 AM, Kevin Kim (Sangwoo) wrote:
> > +1 for gradle,
> > I like it much than maven, too.
> > On Mon Jan 12 2015 at 5:13:17 PM Anthony Corbacho <
> > anthonycorbacho@apache.org> wrote:
> >
> >> If we can come up with a list of things that we need, I can add them.
> >>
> >> On Mon, Jan 12, 2015 at 5:02 PM, moon soo Lee <mo...@apache.org> wrote:
> >>
> >>> +1
> >>>
> >>> it's been very long to have that PR open. I guess it is not that simple
> >> job
> >>> to make all behavior working just as current mvn.
> >>> If it takes too long, i think we can discuss minimum requirement of
> >> gradle
> >>> build. With quick minimum build support pushed to source tree, maybe we
> >> can
> >>> attract people who prefer use gradle and can get chances of feedback
> and
> >>> improvements.
> >>>
> >>> Best,
> >>> moon
> >>>
> >>> 2015년 1월 12일 월요일, Alex B.<bz...@apache.org>님이 작성한 메시지:
> >>>
> >>>> Same here, enthusiastic +1 for gradle
> >>>>
> >>>> After years of mvn I would rather prefer gradle now, although better
> to
> >>>> exercise caution here as having a full featured programming language
> in
> >>>> build file may make things unnecessary complicated too.
> >>>>
> >>>> On Mon, Jan 12, 2015 at 4:40 PM, Roman Shaposhnik <
> >> roman@shaposhnik.org
> >>>> <javascript:;>>
> >>>> wrote:
> >>>>
> >>>>> On Sun, Jan 11, 2015 at 11:34 PM, Anthony Corbacho
> >>>>> <anthonycorbacho@apache.org <javascript:;>> wrote:
> >>>>>> Hi,
> >>>>>>
> >>>>>> Few month back, I started to work on integrating Gradle to zeppelin
> >>>> (pull
> >>>>>> request: pull/171 <https://github.com/NFLabs/zeppelin/pull/171>)
> >>> But I
> >>>>>> didnt had the time to finish and complete it :(
> >>>>>> So the question here is more like, Should we keep on and try to
> >>> switch
> >>>>> from
> >>>>>> mvn to gradle?
> >>>>>> What do you think guys?
> >>>>> FWIW: I'm a huge fan of gradle. Not sure if I can promise
> >>>>> to commit coding cycles, but at least I can share my experiences
> >>>>> via answering questions, etc.
> >>>>>
> >>>>> Thanks,
> >>>>> Roman.
> >>>>>
>

Re: Adding Gradle to Zeppelin

["Kevin (Sangwoo) Kim" <ke...@apache.org>]

+1 for adding SBT. (in the future...)

I found that SBT is quite good for faster iteration process of development.
(with SBT '~' command, it will continuously and incrementally build your
project)
I think that's why Apache Spark project is maintaining Maven and SBT both.

Regards,
Kevin


On Mon Jan 12 2015 at 6:50:54 PM Eric Charles <er...@apache.org> wrote:

> -1
>
> IMHO Maven is good enough for what it needs now.
> SBT would be another option and a more natural fit, especially if we
> plan to add more "scala-like" frameworks in the future (Play...).
>
> Anyway, would it make sense that I jump as maintainer of maven pom(s),
> adding SBT in the future?
> Having two build systems is not ideal, but can help some guys and have a
> broader coverage.
>
> Thx, Eric
>
>
> On 01/12/2015 09:50 AM, Kevin Kim (Sangwoo) wrote:
> > +1 for gradle,
> > I like it much than maven, too.
> > On Mon Jan 12 2015 at 5:13:17 PM Anthony Corbacho <
> > anthonycorbacho@apache.org> wrote:
> >
> >> If we can come up with a list of things that we need, I can add them.
> >>
> >> On Mon, Jan 12, 2015 at 5:02 PM, moon soo Lee <mo...@apache.org> wrote:
> >>
> >>> +1
> >>>
> >>> it's been very long to have that PR open. I guess it is not that simple
> >> job
> >>> to make all behavior working just as current mvn.
> >>> If it takes too long, i think we can discuss minimum requirement of
> >> gradle
> >>> build. With quick minimum build support pushed to source tree, maybe we
> >> can
> >>> attract people who prefer use gradle and can get chances of feedback
> and
> >>> improvements.
> >>>
> >>> Best,
> >>> moon
> >>>
> >>> 2015년 1월 12일 월요일, Alex B.<bz...@apache.org>님이 작성한 메시지:
> >>>
> >>>> Same here, enthusiastic +1 for gradle
> >>>>
> >>>> After years of mvn I would rather prefer gradle now, although better
> to
> >>>> exercise caution here as having a full featured programming language
> in
> >>>> build file may make things unnecessary complicated too.
> >>>>
> >>>> On Mon, Jan 12, 2015 at 4:40 PM, Roman Shaposhnik <
> >> roman@shaposhnik.org
> >>>> <javascript:;>>
> >>>> wrote:
> >>>>
> >>>>> On Sun, Jan 11, 2015 at 11:34 PM, Anthony Corbacho
> >>>>> <anthonycorbacho@apache.org <javascript:;>> wrote:
> >>>>>> Hi,
> >>>>>>
> >>>>>> Few month back, I started to work on integrating Gradle to zeppelin
> >>>> (pull
> >>>>>> request: pull/171 <https://github.com/NFLabs/zeppelin/pull/171>)
> >>> But I
> >>>>>> didnt had the time to finish and complete it :(
> >>>>>> So the question here is more like, Should we keep on and try to
> >>> switch
> >>>>> from
> >>>>>> mvn to gradle?
> >>>>>> What do you think guys?
> >>>>> FWIW: I'm a huge fan of gradle. Not sure if I can promise
> >>>>> to commit coding cycles, but at least I can share my experiences
> >>>>> via answering questions, etc.
> >>>>>
> >>>>> Thanks,
> >>>>> Roman.
> >>>>>
>

Re: Adding Gradle to Zeppelin

[Eric Charles <er...@apache.org>]

-1

IMHO Maven is good enough for what it needs now.
SBT would be another option and a more natural fit, especially if we
plan to add more "scala-like" frameworks in the future (Play...).

Anyway, would it make sense that I jump as maintainer of maven pom(s),
adding SBT in the future?
Having two build systems is not ideal, but can help some guys and have a
broader coverage.

Thx, Eric


On 01/12/2015 09:50 AM, Kevin Kim (Sangwoo) wrote:
> +1 for gradle,
> I like it much than maven, too.
> On Mon Jan 12 2015 at 5:13:17 PM Anthony Corbacho <
> anthonycorbacho@apache.org> wrote:
>
>> If we can come up with a list of things that we need, I can add them.
>>
>> On Mon, Jan 12, 2015 at 5:02 PM, moon soo Lee <mo...@apache.org> wrote:
>>
>>> +1
>>>
>>> it's been very long to have that PR open. I guess it is not that simple
>> job
>>> to make all behavior working just as current mvn.
>>> If it takes too long, i think we can discuss minimum requirement of
>> gradle
>>> build. With quick minimum build support pushed to source tree, maybe we
>> can
>>> attract people who prefer use gradle and can get chances of feedback and
>>> improvements.
>>>
>>> Best,
>>> moon
>>>
>>> 2015년 1월 12일 월요일, Alex B.<bz...@apache.org>님이 작성한 메시지:
>>>
>>>> Same here, enthusiastic +1 for gradle
>>>>
>>>> After years of mvn I would rather prefer gradle now, although better to
>>>> exercise caution here as having a full featured programming language in
>>>> build file may make things unnecessary complicated too.
>>>>
>>>> On Mon, Jan 12, 2015 at 4:40 PM, Roman Shaposhnik <
>> roman@shaposhnik.org
>>>> <javascript:;>>
>>>> wrote:
>>>>
>>>>> On Sun, Jan 11, 2015 at 11:34 PM, Anthony Corbacho
>>>>> <anthonycorbacho@apache.org <javascript:;>> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> Few month back, I started to work on integrating Gradle to zeppelin
>>>> (pull
>>>>>> request: pull/171 <https://github.com/NFLabs/zeppelin/pull/171>)
>>> But I
>>>>>> didnt had the time to finish and complete it :(
>>>>>> So the question here is more like, Should we keep on and try to
>>> switch
>>>>> from
>>>>>> mvn to gradle?
>>>>>> What do you think guys?
>>>>> FWIW: I'm a huge fan of gradle. Not sure if I can promise
>>>>> to commit coding cycles, but at least I can share my experiences
>>>>> via answering questions, etc.
>>>>>
>>>>> Thanks,
>>>>> Roman.
>>>>>

Re: Adding Gradle to Zeppelin

["Kevin Kim (Sangwoo)" <ke...@between.us>]

+1 for gradle,
I like it much than maven, too.
On Mon Jan 12 2015 at 5:13:17 PM Anthony Corbacho <
anthonycorbacho@apache.org> wrote:

> If we can come up with a list of things that we need, I can add them.
>
> On Mon, Jan 12, 2015 at 5:02 PM, moon soo Lee <mo...@apache.org> wrote:
>
> > +1
> >
> > it's been very long to have that PR open. I guess it is not that simple
> job
> > to make all behavior working just as current mvn.
> > If it takes too long, i think we can discuss minimum requirement of
> gradle
> > build. With quick minimum build support pushed to source tree, maybe we
> can
> > attract people who prefer use gradle and can get chances of feedback and
> > improvements.
> >
> > Best,
> > moon
> >
> > 2015년 1월 12일 월요일, Alex B.<bz...@apache.org>님이 작성한 메시지:
> >
> > > Same here, enthusiastic +1 for gradle
> > >
> > > After years of mvn I would rather prefer gradle now, although better to
> > > exercise caution here as having a full featured programming language in
> > > build file may make things unnecessary complicated too.
> > >
> > > On Mon, Jan 12, 2015 at 4:40 PM, Roman Shaposhnik <
> roman@shaposhnik.org
> > > <javascript:;>>
> > > wrote:
> > >
> > > > On Sun, Jan 11, 2015 at 11:34 PM, Anthony Corbacho
> > > > <anthonycorbacho@apache.org <javascript:;>> wrote:
> > > > > Hi,
> > > > >
> > > > > Few month back, I started to work on integrating Gradle to zeppelin
> > > (pull
> > > > > request: pull/171 <https://github.com/NFLabs/zeppelin/pull/171>)
> > But I
> > > > > didnt had the time to finish and complete it :(
> > > > > So the question here is more like, Should we keep on and try to
> > switch
> > > > from
> > > > > mvn to gradle?
> > > > > What do you think guys?
> > > >
> > > > FWIW: I'm a huge fan of gradle. Not sure if I can promise
> > > > to commit coding cycles, but at least I can share my experiences
> > > > via answering questions, etc.
> > > >
> > > > Thanks,
> > > > Roman.
> > > >
> > >
> >
>

Re: Adding Gradle to Zeppelin

[Anthony Corbacho <an...@apache.org>]

If we can come up with a list of things that we need, I can add them.

On Mon, Jan 12, 2015 at 5:02 PM, moon soo Lee <mo...@apache.org> wrote:

> +1
>
> it's been very long to have that PR open. I guess it is not that simple job
> to make all behavior working just as current mvn.
> If it takes too long, i think we can discuss minimum requirement of gradle
> build. With quick minimum build support pushed to source tree, maybe we can
> attract people who prefer use gradle and can get chances of feedback and
> improvements.
>
> Best,
> moon
>
> 2015년 1월 12일 월요일, Alex B.<bz...@apache.org>님이 작성한 메시지:
>
> > Same here, enthusiastic +1 for gradle
> >
> > After years of mvn I would rather prefer gradle now, although better to
> > exercise caution here as having a full featured programming language in
> > build file may make things unnecessary complicated too.
> >
> > On Mon, Jan 12, 2015 at 4:40 PM, Roman Shaposhnik <roman@shaposhnik.org
> > <javascript:;>>
> > wrote:
> >
> > > On Sun, Jan 11, 2015 at 11:34 PM, Anthony Corbacho
> > > <anthonycorbacho@apache.org <javascript:;>> wrote:
> > > > Hi,
> > > >
> > > > Few month back, I started to work on integrating Gradle to zeppelin
> > (pull
> > > > request: pull/171 <https://github.com/NFLabs/zeppelin/pull/171>)
> But I
> > > > didnt had the time to finish and complete it :(
> > > > So the question here is more like, Should we keep on and try to
> switch
> > > from
> > > > mvn to gradle?
> > > > What do you think guys?
> > >
> > > FWIW: I'm a huge fan of gradle. Not sure if I can promise
> > > to commit coding cycles, but at least I can share my experiences
> > > via answering questions, etc.
> > >
> > > Thanks,
> > > Roman.
> > >
> >
>

Re: Adding Gradle to Zeppelin

[moon soo Lee <mo...@apache.org>]

+1

it's been very long to have that PR open. I guess it is not that simple job
to make all behavior working just as current mvn.
If it takes too long, i think we can discuss minimum requirement of gradle
build. With quick minimum build support pushed to source tree, maybe we can
attract people who prefer use gradle and can get chances of feedback and
improvements.

Best,
moon

2015년 1월 12일 월요일, Alex B.<bz...@apache.org>님이 작성한 메시지:

> Same here, enthusiastic +1 for gradle
>
> After years of mvn I would rather prefer gradle now, although better to
> exercise caution here as having a full featured programming language in
> build file may make things unnecessary complicated too.
>
> On Mon, Jan 12, 2015 at 4:40 PM, Roman Shaposhnik <roman@shaposhnik.org
> <javascript:;>>
> wrote:
>
> > On Sun, Jan 11, 2015 at 11:34 PM, Anthony Corbacho
> > <anthonycorbacho@apache.org <javascript:;>> wrote:
> > > Hi,
> > >
> > > Few month back, I started to work on integrating Gradle to zeppelin
> (pull
> > > request: pull/171 <https://github.com/NFLabs/zeppelin/pull/171>) But I
> > > didnt had the time to finish and complete it :(
> > > So the question here is more like, Should we keep on and try to switch
> > from
> > > mvn to gradle?
> > > What do you think guys?
> >
> > FWIW: I'm a huge fan of gradle. Not sure if I can promise
> > to commit coding cycles, but at least I can share my experiences
> > via answering questions, etc.
> >
> > Thanks,
> > Roman.
> >
>

Re: Adding Gradle to Zeppelin

[Roman Shaposhnik <ro...@shaposhnik.org>]

On Sun, Jan 11, 2015 at 11:46 PM, Alex B. <bz...@apache.org> wrote:
> Same here, enthusiastic +1 for gradle
>
> After years of mvn I would rather prefer gradle now, although better to
> exercise caution here as having a full featured programming language in
> build file may make things unnecessary complicated too.

But at least you can unit test your build logic units! ;-)

Thanks,
Roman.

Re: Adding Gradle to Zeppelin

["Alex B." <bz...@apache.org>]

Same here, enthusiastic +1 for gradle

After years of mvn I would rather prefer gradle now, although better to
exercise caution here as having a full featured programming language in
build file may make things unnecessary complicated too.

On Mon, Jan 12, 2015 at 4:40 PM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:

> On Sun, Jan 11, 2015 at 11:34 PM, Anthony Corbacho
> <an...@apache.org> wrote:
> > Hi,
> >
> > Few month back, I started to work on integrating Gradle to zeppelin (pull
> > request: pull/171 <https://github.com/NFLabs/zeppelin/pull/171>) But I
> > didnt had the time to finish and complete it :(
> > So the question here is more like, Should we keep on and try to switch
> from
> > mvn to gradle?
> > What do you think guys?
>
> FWIW: I'm a huge fan of gradle. Not sure if I can promise
> to commit coding cycles, but at least I can share my experiences
> via answering questions, etc.
>
> Thanks,
> Roman.
>

Re: Adding Gradle to Zeppelin

[Roman Shaposhnik <ro...@shaposhnik.org>]

On Sun, Jan 11, 2015 at 11:34 PM, Anthony Corbacho
<an...@apache.org> wrote:
> Hi,
>
> Few month back, I started to work on integrating Gradle to zeppelin (pull
> request: pull/171 <https://github.com/NFLabs/zeppelin/pull/171>) But I
> didnt had the time to finish and complete it :(
> So the question here is more like, Should we keep on and try to switch from
> mvn to gradle?
> What do you think guys?

FWIW: I'm a huge fan of gradle. Not sure if I can promise
to commit coding cycles, but at least I can share my experiences
via answering questions, etc.

Thanks,
Roman.

Re: Adding Gradle to Zeppelin

[Anthony Corbacho <an...@apache.org>]

Hi

@Eran, I alreaady tried this plugin but i didnt like it so i cooked a sh
script that helps me a lot to generate a proper build.gradle.

@Moon, I added your requirement to my list

@Peng Cheng, I am not really sure about that, but i see what you mean. And
for me, if we want to switch now it is the perfect timing.

@Henry, yes having 2 build system doesnt make sense.


On Tue, Jan 13, 2015 at 8:09 PM, IT CTO <go...@gmail.com> wrote:

> just my 2 cents here,
> if the decision will be to move from MVN to Gradle we should look at the
> http://www.gradle.org/docs/current/userguide/build_init_plugin.html which
> provides some bootstraping for Gradle build by converting MVN to Gradle.
>
> Eran
>
> On Mon, Jan 12, 2015 at 11:48 PM, Henry Saputra <he...@gmail.com>
> wrote:
>
> > No good deed goes unpunished :)
> > I am ok with Gradle but if we wanted to go with it we need remove maven
> and
> > go with gradle 100 percent.
> >
> > Have 2 different build system is hard to manage.
> >
> > On Sunday, January 11, 2015, Anthony Corbacho <
> anthonycorbacho@apache.org>
> > wrote:
> >
> > > Hi,
> > >
> > > Few month back, I started to work on integrating Gradle to zeppelin
> (pull
> > > request: pull/171 <https://github.com/NFLabs/zeppelin/pull/171>) But I
> > > didnt had the time to finish and complete it :(
> > > So the question here is more like, Should we keep on and try to switch
> > from
> > > mvn to gradle?
> > > What do you think guys?
> > >
> > > Anthony
> > >
> >
>
>
>
> --
> Eran | CTO
>

Re: Adding Gradle to Zeppelin

[IT CTO <go...@gmail.com>]

just my 2 cents here,
if the decision will be to move from MVN to Gradle we should look at the
http://www.gradle.org/docs/current/userguide/build_init_plugin.html which
provides some bootstraping for Gradle build by converting MVN to Gradle.

Eran

On Mon, Jan 12, 2015 at 11:48 PM, Henry Saputra <he...@gmail.com>
wrote:

> No good deed goes unpunished :)
> I am ok with Gradle but if we wanted to go with it we need remove maven and
> go with gradle 100 percent.
>
> Have 2 different build system is hard to manage.
>
> On Sunday, January 11, 2015, Anthony Corbacho <an...@apache.org>
> wrote:
>
> > Hi,
> >
> > Few month back, I started to work on integrating Gradle to zeppelin (pull
> > request: pull/171 <https://github.com/NFLabs/zeppelin/pull/171>) But I
> > didnt had the time to finish and complete it :(
> > So the question here is more like, Should we keep on and try to switch
> from
> > mvn to gradle?
> > What do you think guys?
> >
> > Anthony
> >
>



-- 
Eran | CTO

Re: Adding Gradle to Zeppelin

[Henry Saputra <he...@gmail.com>]

No good deed goes unpunished :)
I am ok with Gradle but if we wanted to go with it we need remove maven and
go with gradle 100 percent.

Have 2 different build system is hard to manage.

On Sunday, January 11, 2015, Anthony Corbacho <an...@apache.org>
wrote:

> Hi,
>
> Few month back, I started to work on integrating Gradle to zeppelin (pull
> request: pull/171 <https://github.com/NFLabs/zeppelin/pull/171>) But I
> didnt had the time to finish and complete it :(
> So the question here is more like, Should we keep on and try to switch from
> mvn to gradle?
> What do you think guys?
>
> Anthony
>

Re: Adding Gradle to Zeppelin

[Peng Cheng <rh...@gmail.com>]

I'm a long term Maven user/hater but have no experience with Gradle. My
concern is that you may not find as much as plugins if you switch.
As a result. I prone to keep the build system and only switch when
necessary or when there is no tasks with higher priority.

On 12 January 2015 at 12:46, Konstantin Boudnik <co...@apache.org> wrote:

> We are moving Bigtop's build - which is vast - to gradle, removing make and
> mvn in the pass. So hell yeah - go for it ;)
>
> On Mon, Jan 12, 2015 at 04:34PM, Anthony Corbacho wrote:
> > Hi,
> >
> > Few month back, I started to work on integrating Gradle to zeppelin (pull
> > request: pull/171 <https://github.com/NFLabs/zeppelin/pull/171>) But I
> > didnt had the time to finish and complete it :(
> > So the question here is more like, Should we keep on and try to switch
> from
> > mvn to gradle?
> > What do you think guys?
> >
> > Anthony
>

Re: Adding Gradle to Zeppelin

[Konstantin Boudnik <co...@apache.org>]

We are moving Bigtop's build - which is vast - to gradle, removing make and
mvn in the pass. So hell yeah - go for it ;)

On Mon, Jan 12, 2015 at 04:34PM, Anthony Corbacho wrote:
> Hi,
> 
> Few month back, I started to work on integrating Gradle to zeppelin (pull
> request: pull/171 <https://github.com/NFLabs/zeppelin/pull/171>) But I
> didnt had the time to finish and complete it :(
> So the question here is more like, Should we keep on and try to switch from
> mvn to gradle?
> What do you think guys?
> 
> Anthony