Agreed with Alex, too. On Mon Jan 12 2015 at 7:07:11 PM Anthony Corbacho < anthonycorba...@apache.org> wrote:
> I agree with Alex. > > On Mon, Jan 12, 2015 at 7:02 PM, Alex B. <b...@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 <e...@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 < > > > > anthonycorba...@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 <m...@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.<b...@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 > > > >>>> <javascript:;>> > > > >>>> wrote: > > > >>>> > > > >>>>> On Sun, Jan 11, 2015 at 11:34 PM, Anthony Corbacho > > > >>>>> <anthonycorba...@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. > > > >>>>> > > > > > >
