There is a branch already, this is why I mentioned "committing to branch": https://git1-us-west.apache.org/repos/asf?p=lucene-solr.git;a=shortlog;h=refs/heads/jira/gradle
Uwe ----- Uwe Schindler Achterdiek 19, D-28357 Bremen http://www.thetaphi.de eMail: [email protected] > -----Original Message----- > From: Erick Erickson <[email protected]> > Sent: Monday, November 5, 2018 4:27 PM > To: [email protected] > Subject: Re: Call for help: moving from ant build to gradle > > Seems more efficient to put it on a branch for easier collaboration. > On Mon, Nov 5, 2018 at 7:24 AM Michael McCandless > <[email protected]> wrote: > > > > +1 to put latest progress onto a branch and iterate. > > > > Those benefits of Gradle over Ant sound compelling. > > > > Mike McCandless > > > > http://blog.mikemccandless.com > > > > > > On Mon, Nov 5, 2018 at 10:22 AM David Smiley > <[email protected]> wrote: > >> > >> Glad to see this Dat & Uwe! > >> > >> RE "Should we all commit to the branch for proceeding?" > >> > >> In this context do you mean are we "committed" to migrating to Gradle? > (+1 from me). Or that future work should continue to use that branch? It > seems very logical to use a branch. > >> > >> ~ David > >> > >> On Mon, Nov 5, 2018 at 7:46 AM Uwe Schindler <[email protected]> > wrote: > >>> > >>> Hi Đạt, > >>> > >>> > >>> > >>> great work. I had some time to look into it, looks good as a start. I > >>> agree > there is a lot of work to be done, especially the additional tasks for > regenerating sources, extracting data from ICU, quality checks, > documentation (XSLT). Also the transcoder to Java 9+ for MR-JARs is still > missing as a “compile”-like task (I can help with that). > >>> > >>> > >>> > >>> Should we all commit to the branch for proceeding? > >>> > >>> Uwe > >>> > >>> > >>> > >>> ----- > >>> > >>> Uwe Schindler > >>> > >>> Achterdiek 19, D-28357 Bremen > >>> > >>> http://www.thetaphi.de > >>> > >>> eMail: [email protected] > >>> > >>> > >>> > >>> From: Đạt Cao Mạnh <[email protected]> > >>> Sent: Sunday, November 4, 2018 8:13 PM > >>> To: Solr/Lucene Dev <[email protected]> > >>> Subject: Call for help: moving from ant build to gradle > >>> > >>> > >>> > >>> 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! > >>> > >>> > >> > >> -- > >> Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker > >> LinkedIn: http://linkedin.com/in/davidwsmiley | Book: > http://www.solrenterprisesearchserver.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
