3 ms·
Why exactly? It stores caches, that gets used for the build process. How else should it operate? The problem is the amount of dependencies/build tasks, not the
by kaba0 5y ago
Why exactly? It stores caches, that gets used for the build process. How else should it operate?
The problem is the amount of dependencies/build tasks, not the tool managing those.
- pjmlp 5y agoThe excuses with Gradle are always the kind of "you're holding it wrong". Thankfully outside Android, I never have to put up with it on regular Java projects.
- kaba0 5y agoWhich would show you how is it a very fast build tool, but if you prefer not even learning about it, do stay in your ignorance.
- deleted 5y ago[deleted]
- pjmlp 5y agoYet again the "holding it wrong" and "you're an ignorant" argument that always comes up from Gradle people. Yeah, it is very fast, when one has all the knobs to help Gradle pretend it is fast. I have been setting up Java CI/CD pipelines since 2005, have used all major CI/CD products in the Java world, including your beloved "blazing fast" Gradle.