any reason for discriminating against a build system that supports customised lifecycles (e.g. maven)?
un saludo ________________________________ From: Diego Ceccarelli (BLOOMBERG/ LONDON) <dceccarel...@bloomberg.net> Sent: Wednesday, November 21, 2018 5:30 AM To: dev@lucene.apache.org Subject: Re: Call for help: moving from ant build to gradle Hi all, I just noticed this thread I would be happy to help if I can. I checked out the jira/gradle branch but I get conflicts if I try to rebase on top of the current master.. Do you have a list of subtasks for porting solr to gradle? Thanks, Diego From: dev@lucene.apache.org At: 11/05/18 22:34:50 To: dev@lucene.apache.org<mailto:dev@lucene.apache.org> Subject: Re: Call for help: moving from ant build to gradle Edward: Of course. You may have to coordinate how to get your contributions added to the patch is all. I'd coordinate with Dat first though just for efficiency's sake. Just work with the branch/gradle version of the code from the main Git repo. On Mon, Nov 5, 2018 at 2:22 PM Edward Ribeiro <edward.ribe...@gmail.com<mailto:edward.ribe...@gmail.com>> wrote: > > Is this work open to contribution of non committers? > > Edward > > > Em seg, 5 de nov de 2018 15:01, Gus Heck > <gus.h...@gmail.com<mailto:gus.h...@gmail.com> escreveu: >> >> I'm quite fond of gradle, and even wrote a very simple plugin for uploading and downloading solr configs to zookeeper from gradle. +1 to use gradle. >> >> I'll definitely check it out and give it a whirl, maybe I'll help some if I can. >> >> On Sun, Nov 4, 2018 at 2:13 PM Đạt Cao Mạnh >> <caomanhdat...@gmail.com<mailto:caomanhdat...@gmail.com>> wrote: >>> >>> Hi guys, >>> >>> Recently, I had a chance of working on modifying different build.xml of our project. To be honest that was a painful experience, especially the number of steps for adding a new module in our project. We reach the limitation point of Ant and moving to Gradle seems a good option since it has been widely used in many projects. There are several benefits of the moving here that I would like to mention >>> * The capability of caching result in Gradle make running task much faster. I.e: rerunning forbiddenApi check in Gradle only takes 5 seconds (comparing to more than a minute of Ant). >>> * Adding modules is much easier now. >>> * Adding dependencies is a pleasure now since we don't have to run ant clean-idea and ant idea all over again. >>> * Natively supported by different IDEs. >>> >>> On my very boring long flight from Montreal back to Vietnam, I tried to convert the Lucene/Solr Ant to Gradle, I finally achieved something here by being able to import project and run tests natively from IntelliJ IDEA (branch jira/gradle). >>> >>> I'm converting ant precommit for Lucene to Gradle. But there are a lot of things need to be done here and my limitation understanding in our Ant build and Gradle may make the work take a lot of time to finish. >>> >>> Therefore, I really need help from the community to finish the work and we will be able to move to a totally new, modern, powerful build tool. >>> >>> Thanks! >>> >> >> >> -- >> http://www.the111shift.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org<mailto:dev-unsubscr...@lucene.apache.org> For additional commands, e-mail: dev-h...@lucene.apache.org<mailto:dev-h...@lucene.apache.org>
