Call for help: moving from ant build to gradle

classic Classic list List threaded Threaded
39 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Call for help: moving from ant build to gradle

caomanhdat
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!

Reply | Threaded
Open this post in threaded view
|

RE: Call for help: moving from ant build to gradle

Uwe Schindler

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: [hidden email]

 

From: Đạt Cao Mạnh <[hidden email]>
Sent: Sunday, November 4, 2018 8:13 PM
To: Solr/Lucene Dev <[hidden email]>
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!

 

Reply | Threaded
Open this post in threaded view
|

Re: Call for help: moving from ant build to gradle

david.w.smiley@gmail.com
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 <[hidden email]> 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: [hidden email]

 

From: Đạt Cao Mạnh <[hidden email]>
Sent: Sunday, November 4, 2018 8:13 PM
To: Solr/Lucene Dev <[hidden email]>
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
Reply | Threaded
Open this post in threaded view
|

Re: Call for help: moving from ant build to gradle

Michael McCandless-2
+1 to put latest progress onto a branch and iterate.

Those benefits of Gradle over Ant sound compelling.


On Mon, Nov 5, 2018 at 10:22 AM David Smiley <[hidden email]> 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 <[hidden email]> 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: [hidden email]

 

From: Đạt Cao Mạnh <[hidden email]>
Sent: Sunday, November 4, 2018 8:13 PM
To: Solr/Lucene Dev <[hidden email]>
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
Reply | Threaded
Open this post in threaded view
|

Re: Call for help: moving from ant build to gradle

Erick Erickson
Seems more efficient to put it on a branch for easier collaboration.
On Mon, Nov 5, 2018 at 7:24 AM Michael McCandless
<[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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: [hidden email]
>>>
>>>
>>>
>>> From: Đạt Cao Mạnh <[hidden email]>
>>> Sent: Sunday, November 4, 2018 8:13 PM
>>> To: Solr/Lucene Dev <[hidden email]>
>>> 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Call for help: moving from ant build to gradle

Uwe Schindler
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: [hidden email]

> -----Original Message-----
> From: Erick Erickson <[hidden email]>
> Sent: Monday, November 5, 2018 4:27 PM
> To: [hidden email]
> 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
> <[hidden email]> 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
> <[hidden email]> 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 <[hidden email]>
> 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: [hidden email]
> >>>
> >>>
> >>>
> >>> From: Đạt Cao Mạnh <[hidden email]>
> >>> Sent: Sunday, November 4, 2018 8:13 PM
> >>> To: Solr/Lucene Dev <[hidden email]>
> >>> 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: [hidden email]
> For additional commands, e-mail: [hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Call for help: moving from ant build to gradle

caomanhdat
Hi Uwe, yeah I think we should continue working on that branch, I will do regularly make it up to date with master branch. 

On Mon, Nov 5, 2018 at 3:44 PM Uwe Schindler <[hidden email]> wrote:
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: [hidden email]

> -----Original Message-----
> From: Erick Erickson <[hidden email]>
> Sent: Monday, November 5, 2018 4:27 PM
> To: [hidden email]
> 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
> <[hidden email]> 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
> <[hidden email]> 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 <[hidden email]>
> 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: [hidden email]
> >>>
> >>>
> >>>
> >>> From: Đạt Cao Mạnh <[hidden email]>
> >>> Sent: Sunday, November 4, 2018 8:13 PM
> >>> To: Solr/Lucene Dev <[hidden email]>
> >>> 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: [hidden email]
> For additional commands, e-mail: [hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Call for help: moving from ant build to gradle

Gus Heck
In reply to this post by caomanhdat
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 <[hidden email]> 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!



--
Reply | Threaded
Open this post in threaded view
|

Re: Call for help: moving from ant build to gradle

Edward Ribeiro
Is this work open to contribution of non committers?

Edward


Em seg, 5 de nov de 2018 15:01, Gus Heck <[hidden email] 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 <[hidden email]> 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!



--
Reply | Threaded
Open this post in threaded view
|

Re: Call for help: moving from ant build to gradle

Erick Erickson
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 <[hidden email]> wrote:

>
> Is this work open to contribution of non committers?
>
> Edward
>
>
> Em seg, 5 de nov de 2018 15:01, Gus Heck <[hidden email] 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 <[hidden email]> 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Call for help: moving from ant build to gradle

Yago Riveiro
In reply to this post by david.w.smiley@gmail.com

Yago Riveiro smiled at you

Best regards /Yago
Reply | Threaded
Open this post in threaded view
|

Re: Call for help: moving from ant build to gradle

Mark Miller-3
In reply to this post by caomanhdat
+1. Gradle is the alpha and the omega of build systems. I will help.

- Mark

On Sun, Nov 4, 2018 at 1:13 PM Đạt Cao Mạnh <[hidden email]> 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!



--
Reply | Threaded
Open this post in threaded view
|

Re: Call for help: moving from ant build to gradle

Vladimir Kroz
+1 for moving to gradle. I'm happy to help.

On Wed, Dec 19, 2018 at 8:25 AM Mark Miller <[hidden email]> wrote:
+1. Gradle is the alpha and the omega of build systems. I will help.

- Mark

On Sun, Nov 4, 2018 at 1:13 PM Đạt Cao Mạnh <[hidden email]> 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!



--


--
Best regards, 

Vladimir Kroz
Phone: (707) 515-9195
Reply | Threaded
Open this post in threaded view
|

Re: Call for help: moving from ant build to gradle

Gézapeti
I'd be happy to help with the gradle migration.
I could not find a jira that covers it, only LUCENE-5755, which was closed a long time ago.
Where can I join the discussion about this?

Thanks for the pointers,
gp


On Thu, Feb 7, 2019 at 8:23 PM Vladimir Kroz <[hidden email]> wrote:
+1 for moving to gradle. I'm happy to help.

On Wed, Dec 19, 2018 at 8:25 AM Mark Miller <[hidden email]> wrote:
+1. Gradle is the alpha and the omega of build systems. I will help.

- Mark

On Sun, Nov 4, 2018 at 1:13 PM Đạt Cao Mạnh <[hidden email]> 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!



--


--
Best regards, 

Vladimir Kroz
Phone: (707) 515-9195
Reply | Threaded
Open this post in threaded view
|

Re: Call for help: moving from ant build to gradle

Martin Gainty
your argument that gradle is faster than maven is based on internal caching algorithm that gradle references

IF you are *NOT* politically endangered from implementing maven i encourage you to take a hard look at 

"implementing caching of maven artifacts using cache-proxies"
https://support.sonatype.com/hc/en-us/articles/115010182627-Understanding-Caching-Configuration

as you can see speed is achieved when local proxy-cache is referenced BEFORE far-flung remote repositories

by properly tuning local cache-proxies you can bypass high-latency remote repositories and "accelerate your build process"

/greets/
martin-

From: Gézapeti <[hidden email]>
Sent: Monday, March 4, 2019 5:45 PM
To: [hidden email]
Cc: [hidden email]
Subject: Re: Call for help: moving from ant build to gradle
 
I'd be happy to help with the gradle migration.
I could not find a jira that covers it, only LUCENE-5755, which was closed a long time ago.
Where can I join the discussion about this?

Thanks for the pointers,
gp


On Thu, Feb 7, 2019 at 8:23 PM Vladimir Kroz <[hidden email]> wrote:
+1 for moving to gradle. I'm happy to help.

On Wed, Dec 19, 2018 at 8:25 AM Mark Miller <[hidden email]> wrote:
+1. Gradle is the alpha and the omega of build systems. I will help.

- Mark

On Sun, Nov 4, 2018 at 1:13 PM Đạt Cao Mạnh <[hidden email]> 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!



--


--
Best regards, 

Vladimir Kroz
Phone: (707) 515-9195
Reply | Threaded
Open this post in threaded view
|

Re: Call for help: moving from ant build to gradle

Diego Ceccarelli
Hi Đạt and all, 

I made some progress starting from Đạt's patch:

- Now the patch compiles all the projects, and can be applied to the upstream version
- I removed the changes to the source/test paths, and override the default gradle paths to the one used by ant (so future commits will not create conflicts)


You can play with the patch by running:


from master, followed by './gradlew build'

There is still a lot of work to do:
- I didn't touch the tests (they might not compile) 
- I tried to load it on intellij as a gradle project and it didn't work
- it doesn't produce a standalone jar 
- some dependencies are probably out of sync, we should have something to read them directly from the ivy configuration, or a script to convert them.. 

Please let me know if you have any comments, PR are very welcome :) 

Thanks,
Diego












On Thu, Mar 7, 2019 at 8:08 AM Martin Gainty <[hidden email]> wrote:
your argument that gradle is faster than maven is based on internal caching algorithm that gradle references

IF you are *NOT* politically endangered from implementing maven i encourage you to take a hard look at 

"implementing caching of maven artifacts using cache-proxies"
https://support.sonatype.com/hc/en-us/articles/115010182627-Understanding-Caching-Configuration
Proxy repositories use caching to improve build performance. The settings you can use to configure caching are described in this article....

as you can see speed is achieved when local proxy-cache is referenced BEFORE far-flung remote repositories

by properly tuning local cache-proxies you can bypass high-latency remote repositories and "accelerate your build process"

/greets/
martin-

From: Gézapeti <[hidden email]>
Sent: Monday, March 4, 2019 5:45 PM
To: [hidden email]
Cc: [hidden email]
Subject: Re: Call for help: moving from ant build to gradle
 
I'd be happy to help with the gradle migration.
I could not find a jira that covers it, only LUCENE-5755, which was closed a long time ago.
Where can I join the discussion about this?

Thanks for the pointers,
gp


On Thu, Feb 7, 2019 at 8:23 PM Vladimir Kroz <[hidden email]> wrote:
+1 for moving to gradle. I'm happy to help.

On Wed, Dec 19, 2018 at 8:25 AM Mark Miller <[hidden email]> wrote:
+1. Gradle is the alpha and the omega of build systems. I will help.

- Mark

On Sun, Nov 4, 2018 at 1:13 PM Đạt Cao Mạnh <[hidden email]> 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!



--


--
Best regards, 

Vladimir Kroz
Phone: (707) 515-9195
Reply | Threaded
Open this post in threaded view
|

Re: Call for help: moving from ant build to gradle

caomanhdat
Cool Diego,

I will take a look on this. Thanks a lot!
Reply | Threaded
Open this post in threaded view
|

Re: Call for help: moving from ant build to gradle

Mark Miller-3
I've got my own lucene-solr gradle branch as well.

I stole the BuildPlugin and CheckWorkingCopy from Dat's branch, but also made some changes.

* Similar to above above, I don't move the src files so it can keep things up to date without lots of pain.
* I used a plugin that lets us define versions in a root props file like we currently do and ensures we use the same versions in all modules even after auto conflict resolution (unlike gradle by default)
* It also locks versions so we can continue to pay attention to scary automatic dependency resolution changes
* implementation and api used instead of compile
* Things build and the majority of tests pass (Lucene's TestVirtualMethod does not for example) 

If someone like Uwe is serious about helping out with fun extras (regenerating sources, extracting data from ICU, quality checks, documentation (XSLT)), I'd look at contributing.

- Mark


On Mon, Apr 8, 2019 at 9:44 AM Đạt Cao Mạnh <[hidden email]> wrote:
Cool Diego,

I will take a look on this. Thanks a lot!


--
Reply | Threaded
Open this post in threaded view
|

Re: Call for help: moving from ant build to gradle

Mark Miller-3
I looked into this a little more.

Seems if we just do it with master and going forward, we don’t need multi version support - Uwe seems to have taken it out with the move to Java 11?

I can handle regenerate.

The other quality checks shouldn’t be crazy. 

So I guess we can probably do this, but before I focus on BS details, please speak up if you hate the idea of Gradle and you have the clout to stop it. 


Mark




On Sat, May 4, 2019 at 5:56 PM Mark Miller <[hidden email]> wrote:
I've got my own lucene-solr gradle branch as well.

I stole the BuildPlugin and CheckWorkingCopy from Dat's branch, but also made some changes.

* Similar to above above, I don't move the src files so it can keep things up to date without lots of pain.
* I used a plugin that lets us define versions in a root props file like we currently do and ensures we use the same versions in all modules even after auto conflict resolution (unlike gradle by default)
* It also locks versions so we can continue to pay attention to scary automatic dependency resolution changes
* implementation and api used instead of compile
* Things build and the majority of tests pass (Lucene's TestVirtualMethod does not for example) 

If someone like Uwe is serious about helping out with fun extras (regenerating sources, extracting data from ICU, quality checks, documentation (XSLT)), I'd look at contributing.

- Mark


On Mon, Apr 8, 2019 at 9:44 AM Đạt Cao Mạnh <[hidden email]> wrote:
Cool Diego,

I will take a look on this. Thanks a lot!


--
--
Reply | Threaded
Open this post in threaded view
|

Re: Call for help: moving from ant build to gradle

Ishan Chattopadhyaya
Would beasting of tests be possible through gradle?

On Sun, May 5, 2019 at 7:33 AM Mark Miller <[hidden email]> wrote:

>
> I looked into this a little more.
>
> Seems if we just do it with master and going forward, we don’t need multi version support - Uwe seems to have taken it out with the move to Java 11?
>
> I can handle regenerate.
>
> The other quality checks shouldn’t be crazy.
>
> So I guess we can probably do this, but before I focus on BS details, please speak up if you hate the idea of Gradle and you have the clout to stop it.
>
>
> Mark
>
>
>
>
> On Sat, May 4, 2019 at 5:56 PM Mark Miller <[hidden email]> wrote:
>>
>> I've got my own lucene-solr gradle branch as well.
>>
>> I stole the BuildPlugin and CheckWorkingCopy from Dat's branch, but also made some changes.
>>
>> * Similar to above above, I don't move the src files so it can keep things up to date without lots of pain.
>> * I used a plugin that lets us define versions in a root props file like we currently do and ensures we use the same versions in all modules even after auto conflict resolution (unlike gradle by default)
>> * It also locks versions so we can continue to pay attention to scary automatic dependency resolution changes
>> * implementation and api used instead of compile
>> * Things build and the majority of tests pass (Lucene's TestVirtualMethod does not for example)
>>
>> If someone like Uwe is serious about helping out with fun extras (regenerating sources, extracting data from ICU, quality checks, documentation (XSLT)), I'd look at contributing.
>>
>> - Mark
>>
>>
>> On Mon, Apr 8, 2019 at 9:44 AM Đạt Cao Mạnh <[hidden email]> wrote:
>>>
>>> Cool Diego,
>>>
>>> I will take a look on this. Thanks a lot!
>>
>>
>>
>> --
>> - Mark
>>
>> http://about.me/markrmiller
>
> --
> - Mark
>
> http://about.me/markrmiller

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

12