Many problems we saw in the last years were not particularly Gradle issues. People used to talk about those two interchangeably, especially at times were the version names of both were pretty similar. Let’s clarify one thing:Īndroid-Gradle-Plugin != Gradle. There are issues with Databinding: „Oh f_ck Gradle!“. Publishing a library is confusing: „Oh f_ck Gradle!“. Especially in the Android community, we often see Gradle being blamed for almost everything: Builds are slow: „Oh f_ck Gradle!“.
The true source of all evilīut before we start fixing our problems with Gradle, let’s try to identify what the „true source of all evil“ is. They knew the answers… The knew how to tame the beast and I was absolutely thrilled by their skills! In this article, I would like to share our team’s path to „Gradle Mastery“ and how easily you can become the guy taming the beast. Almost everyone was doing it exactly like this.Įxcept, some Gradle wizards. Talking to other developers at meetups revealed: This was not just us. It was the circle of „Gradle issues“ and I felt that everyone in the team handled it pretty similar. I did this until some small snippet „solved“ the problem, unknowingly that this will cause some other issue later. All I could then do is copy and paste small little snippets from Stackoverflow, not understanding a single bit what they do and hoping they would work.
Whenever I ran into a „Gradle issue“ during Android development, I immediately knew: This is going to be a bad day. It was always one of the biggest pain points in my carrier as a developer. Let’s talk about the elephant in the room… Gradle…
0 kommentar(er)
