I have written several articles about Gradle. This article is the conclusion of the series.
Gradle series
[Android repair manual] Gradle – basic use of Gradle [Android repair manual] Gradle – Android Plugin Plugin main process [Android repair manual] Gradle – Android Gradle Plugin main Task analysis [Android training manual] Gradle chapter – Gradle source code analysis animation explains Gradle principle
About the Gradle
Compared to Android developers, including me at the very beginning, Gradle is just a packaging tool. Usually, I mainly work on app development, but I don’t invest much in Gradle. But when you really dig into it, Gradle can do a lot of things. The learning of Android Gradle Plugin will also deepen the understanding of Android. In fact, sometimes Android development is not just to make an App. For example, when I started to write some small tools, I mostly used Python. Later, after learning Gradle, I may feel that Gradle is easier to use and more convenient. Learning Gradle well will be of great benefit to you later on.
Some try
The logic of the previous article is based on the principle from use to in-depth implementation, which should also conform to the general cognition. I also hope that this series of articles can help some friends who want to learn Gradle. In fact, while writing the article, I also made some attempts to explain some principles in a more concise way, so I added a lot of schematic diagrams in the process of writing, but after looking back, I may not have achieved the desired effect. Because some of these principles and implementation, with schematic way to explain, it is still a little difficult. These days I have an idea to explain the source code in the form of animation. So I tried to do an animation of Gradle principle. Click the link below to watch the animated video. This is the first time to do this kind of animation, maybe the effect is not very good, if you have any suggestions or comments, welcome to leave a comment. Animation explains Gradle principle