Part 3 of the 'How Gradle Works' series explains what happens during Gradle build script execution. It covers the Kotlin and Groovy DSLs used in build scripts, demystifying implicit rules like lambda/closure syntax and chained method invocations. The post also explains how Gradle resolves the chicken-and-egg problem of external dependencies in build scripts by extracting and executing the `plugins {}` block before compiling the rest of the script, then adding resolved dependencies to the classpath before full compilation and execution.

5m read timeFrom blog.gradle.org
Post cover image
Table of contents
Table of ContentsIntroductionKotlin & Groovy DSL #Build Script Execution #External Dependencies in Build Script #What’s Next #Discuss

Sort: