What makes a good build.gradle?
A build.gradle usually starts out innocently enough as a simple, easy to understand file. After all, that’s why you (or someone on your team) chose Gradle as your build system! However, if you don’t spend time refactoring it and give it the love and attention it needs and deserves, it can go awry fairly quickly and come back to haunt you at 1am when you should really be out drinking sleeping, not fiddling with your project’s broken Gradle build. You can end up with a file hundreds of lines long nobody on your team wants to touch or even look at. In this post, I will explain what I think makes a good build.gradle and outline a few strategies or things to consider in order to keep it that way.
My perspective on builds is shaped by many years spent working on build and deployment automation systems in a corporate environment where you will generally find many similar types of projects...
