0Pricing
Groovy & Gradle: JVM Automation and Build Engineering · Lesson

Multi-Project Builds & the Settings File

Organize larger codebases with Gradle multi-project builds, the settings.gradle file, and shared configuration across subprojects.

Why Multi-Project Builds?

Real applications often split into modules — an API, a core library, a CLI. Gradle multi-project builds let one build coordinate many subprojects, sharing configuration and dependencies.

The settings.gradle File

The root settings.gradle defines the build: its name and which subprojects belong to it. Without an include entry, Gradle ignores a directory.

rootProject.name = 'my-app'
include 'core', 'api', 'cli'

All lessons in this course

  1. Gradle Installation & CLI
  2. Gradle Project Structure
  3. Tasks and Build Lifecycle
  4. Multi-Project Builds & the Settings File
← Back to Groovy & Gradle: JVM Automation and Build Engineering