-
Notifications
You must be signed in to change notification settings - Fork 40.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Port the build to Gradle #19608
Comments
Hi @wilkinsona. I maybe have a stupid question. Isn't that breaking the semi automatic dependency upgrade process? And is there maybe a replacement for it? Could you elaborate on the reasoning behind moving to Gradle other than publishing metadata for the modules? Where there any problems with the Maven tooling? Cheers, |
It's built into the build now:
The Gradle metadata is really just an added bonus. The main motivation was to be able to reduce build times by parallelising the build (something we couldn't do in Maven due to our use of the Invoker plugin) and to take full advantage of Gradle's build cache. |
Are the build times of 8-10 minutes correct? That would be an amazing improvement. 🚀 |
Yep, they're correct. Things won't always be that good as that's pretty much a best-case scenario where there are lots of cache hits. |
No description provided.
The text was updated successfully, but these errors were encountered: