Gradle in Action (Benjamin Muschko)（Z-Library）

【One-Line Pitch】 A practical, example-driven guide to automating Java project builds with Gradle, taking you from first scripts to full continuous delivery. Best for Java developers, build engineers, and teams migrating from Ant or Maven who want reproducible, scalable automation. 【Book Arc】 - **Opening (~0%–10%)**: Frames why build automation matters and surveys the Java build-tool landscape, contrasting Ant's flexibility-without-structure against Maven's rigid conventions to set up Gradle's value proposition. - **Early (~10%–32%)**: Introduces Gradle's core model — ordered tasks, dependencies, plugins, and the Groovy DSL — then applies them by bootstrapping a real To Do web application with the Java and WAR plugins. - **Middle (~32%–48%)**: Deepens build-script essentials: task actions, `doFirst`/`doLast`, task properties, custom task classes, task rules, and organizing reusable build code under `buildSrc`. - **Late (~48%–70%)**: Covers dependency management (transitive dependencies, the local cache, version conflicts, insight reports) and multiproject builds (settings files, subproject configuration, cross-project dependencies, partial builds). - **Late (~70%–85%)**: Addresses testing (unit, integration, functional; the test automation pyramid) and code quality/monitoring within the build. - **Ending (~85%–100%)**: Extends into the wider ecosystem — continuous integration, target-environment setup, and deployment — positioning Gradle within a delivery pipeline. 【Key Takeaways】 - **Builds are ordered, executable tasks** (Early): Gradle models automation as tasks with explicit `dependsOn` relationships, giving structure that Ant lacked while staying more flexible than Maven's fixed lifecycle. - **Convention over configuration, but customizable** (Early): Plugins like Java and WAR supply sensible defaults (layouts, tasks), yet properties, manifests, and directory structures can all be overridden when your project deviates. - **Dependency management is first-class** (Late): Gradle resolves transitive dependencies, caches artifacts locally, and offers tooling for version conflicts, forced versions, and cache refresh — solving pain points the book attributes to earlier tools. - **Incremental and partial builds save time** (Early/Late): By declaring task inputs/outputs, Gradle skips or rebuilds only what changed, extending to multimodule projects so you stop running `clean` reflexively. - **Multiproject builds are modular by design** (Late): A settings file plus per-project build scripts let subprojects define their own dependencies and run independently, with Gradle handling rebuild ordering. - **Testing belongs in the build** (Late): Automated unit, integration, and functional tests integrate into the pipeline, with parallel execution to use available cores. - **Build logic deserves real engineering** (Middle): Custom task classes and the `buildSrc` directory let you structure, reuse, and even test build code instead of letting scripts sprawl. - **The build is part of a delivery ecosystem** (Ending): Gradle is framed as integrating with continuous integration, environment setup, and deployment, not as an isolated tool. 【Reading Tips】 - Read the Opening and Early chapters closely for the task/plugin mental model; this foundation makes everything later click. - Skim the Ant/Maven comparison if you already know those tools — extract the "why Gradle" arguments rather than the history. - Treat the To Do application walkthrough as a hands-on lab; typing the examples teaches more than reading them. - Slow down on dependency management and multiproject builds (Late) — these are the highest-value, highest-complexity sections for real projects. - Use the `buildSrc` and custom-task material as a reference when your own build scripts start growing. 【Coverage Limits】 This guide is synthesized from stratified excerpts covering roughly the first half of the book in detail, with later chapters (testing, CI, deployment) represented mainly by table-of-contents entries and brief mentions. Specific later-chapter examples, figures, and code are not covered here.