liveBook · Manning

Gradle

Gradle is an open-source build automation system for defining and executing software build tasks and managing project dependencies.

How 4 Manning books explain it

Fast by Default

Gradle is a build automation system with a programmable model for compiling, testing, packaging, and resolving dependencies.

How it is used
Uses Gradle to inspect dependency graphs and identify libraries inflating Java application artifacts.
How deep it goes
Explains dependency paths, version selection, JAR contents, and native payloads, but does not detail Gradle build-script configuration.
Examples
Demonstrates runtimeClasspath reports, Spring Boot JAR inspection, and tracing oversized dependencies to their originating paths.
What you can do after
Diagnose/debug with it: trace oversized runtime dependencies and select smaller or platform-specific alternatives.

Read how Fast by Default explains Gradle →

Developer Experience on Kubernetes

Gradle is a build automation tool for defining and executing software build workflows, including dependency management and testing.

How it is used
Runs a Java service and its development dependency as part of the inner-loop application startup workflow.
How deep it goes
Defines Gradle as a Java build tool and explains bootRun behavior, but does not detail build configuration or task internals.
Examples
Uses ./gradlew bootRun to launch the appointments service before testing its HTTP endpoint.
What you can do after
Operate a Spring Boot service locally with its PostgreSQL dependency by running the Gradle wrapper.

Read how Developer Experience on Kubernetes explains Gradle →

Kafka Streams in Action, Second Edition

Gradle is a build automation tool that defines and executes project tasks, dependency management, and source-generation workflows.

How it is used
Manages schema registration, compatibility checks, and generated application objects in schema-driven projects.
How deep it goes
Explains plugin roles and demonstrates a configured registration task, without detailing Gradle’s broader build lifecycle.
Examples
Uses an Avro schema, streams/build.gradle configuration, and the ./gradlew streams:registerSchemasTask command.
What you can do after
Operate/configure schema plugins to register schemas and generate Java objects from supported schema formats.

Read how Kafka Streams in Action, Second Edition explains Gradle →

Microservices Patterns, Second Edition

An open-source build automation system that models builds as tasks and supports dependency management and incremental execution.

How it is used
Uses Gradle to make build-time coupling and its effect on developer feedback concrete.
How deep it goes
Explains how coupling changes recompilation and retesting scope, from changed subprojects to an entire component.
Examples
Contrasts rebuilding only changed subprojects with rebuilding and retesting the entire component.
What you can do after
Evaluate how build-time coupling expands recompilation and retesting after a change.

Read how Microservices Patterns, Second Edition explains Gradle →

Also covered in

What to know first

Related concepts

Questions about Gradle

What is Gradle?

Gradle is an open-source build automation system for defining and executing software build tasks and managing project dependencies.

Which Manning books explain Gradle?

Fast by Default, Developer Experience on Kubernetes, Kafka Streams in Action, Second Edition and Microservices Patterns, Second Edition.

What should I know before learning Gradle?

Manning books that teach Gradle usually introduce Go, JAR file, Java and Kotlin first.

What is the difference between Gradle and Maven?

Gradle is an open-source build automation system for defining and executing software build tasks and managing project dependencies. Apache Maven is a build automation and project management tool that manages dependencies and build lifecycles, especially for Java and other JVM projects.

What is Gradle a kind of?

Gradle is a kind of build system. A build system is software that automates transforming source code and project inputs into artifacts through tasks such as compiling, testing, and packaging.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.