Gradle Without The Guesswork: A Guide for Kotlin Developers
summary
Explains why Gradle is a platform driven by plugins, shows the three-phase lifecycle and how tasks are inputs->outputs, and teaches concrete fixes: switch the gradle wrapper suffix from gradle-wrapper.properties from -bin to -all to get sources, prefer register vs create and use configureEach to preserve laziness, rename build files and update settings to avoid duplicate class names when debugging, and disable build/configuration caches or the daemon while stepping through JVM-attached builds so breakpoints actually hit.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:45Why Gradle matters
- 3:11Gradle as build system
- 6:02Plugins and extensions
- 8:06Tasks and dependencies
- 10:12Build lifecycle phases
- 12:40Dependency management
- 14:08Optimizing builds with caching
- 18:05Configuration cache
- 20:10Lazy configuration
- 23:44Task configuration mistakes
- 25:49Debugging build scripts
- 36:31Closing thoughts
related talks
33mUnderstanding Gradle and writing your own Gradle Plugin
33mGradle with Kotlin
56mDeep Dive into the Android Gradle Plugin
35mHow to write Gradle plugins (in Kotlin)
34mGradle scripts in Kotlin: is it cool?
48mType-Safe Build Logic with Gradle Kotlin DSL
44mGradle: The Build System That Loves To Hate You
51mGradle Plugin, Take Control of the Build!