liveBook · Manning

Gradle

As explained in Fast by Default

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

Gradle automates Java build dependency analysis, showing how libraries enter a project, which versions it selects, and which packages contribute to runtime size. section 8.2.2

Use the dependency report to:

  • Trace an unexpectedly large dependency back to the shortest path from application code. section 8.2.2
  • Inspect runtime dependencies, embedded libraries, reflection-heavy packages, and platform-specific native binaries. section 8.2.2
  • Replace unnecessary or oversized dependencies with lighter alternatives when production targets are fixed. section 8.2.2

Inspect the runtime classpath

Run ./gradlew dependencies --configuration runtimeClasspath to list every runtime dependency and reveal how Gradle selected versions when libraries conflict. section 8.2.2

./gradlew dependencies --configuration runtimeClasspath

Explore the Gradle command for listing dependencies on the runtime classpath. section 8.2.2

How Fast by Default covers it

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 it assumes
Assumes familiarity with Java applications, dependencies, JAR files, and runtime classpaths.
What you can do after
Diagnose/debug with it: trace oversized runtime dependencies and select smaller or platform-specific alternatives.
How it connects
Connects dependency analysis with Maven, Spring Boot, Java modules, reflection, and native binaries.

Also explained in

Compare how 4 books explain Gradle →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Fast by Default. The section links point to the parts of the book it draws on.