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 [https://theme.zdassets.com/theme_assets/17748/b23a916dda693a523d66cc6230806788eaa710b6.png]<https://support.sonatype.com/hc/en-us/articles/115010182627-Understanding-Caching-Configuration> Understanding Caching Configuration – Sonatype Support<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.... support.sonatype.com 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 <gezap...@gmail.com> Sent: Monday, March 4, 2019 5:45 PM To: dev@lucene.apache.org Cc: markrmil...@gmail.com 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 <vladimir.k...@gmail.com<mailto:vladimir.k...@gmail.com>> wrote: +1 for moving to gradle. I'm happy to help. On Wed, Dec 19, 2018 at 8:25 AM Mark Miller <markrmil...@gmail.com<mailto:markrmil...@gmail.com>> 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 <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! -- - Mark http://about.me/markrmiller -- Best regards, Vladimir Kroz www.linkedin.com/in/vkroz<http://www.linkedin.com/in/vkroz> Phone: (707) 515-9195
