Groovy & Gradle: JVM Automation and Build Engineering · Pelajaran

Subproyek & Konfigurasi

Definisikan dan konfigurasikan subproyek, serta pahami cara subproyek berinteraksi dalam pembangunan multi-proyek.

Subproyek & Konfigurasi adalah pelajaran Groovy & Gradle: JVM Automation and Build Engineering gratis di CoddyKit. Ini adalah pelajaran 2 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Groovy & Gradle: JVM Automation and Build Engineering, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Groovy & Gradle: JVM Automation and Build Engineering mencakup 4 pelajaran total.

Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.

Welcome to Subprojects!

In large software projects, keeping everything in one giant build file can get messy. This is where subprojects come in handy!

Subprojects allow you to break down a big project into smaller, manageable modules. Think of them as mini-projects living within your main project.

Modularity: Organize code logically.
Reusability: Share common logic across modules.
Faster Builds: Gradle can optimize builds by only working on changed subprojects.

Declaring Subprojects

To tell Gradle about your subprojects, you use the settings.gradle file. This file lives in your root project directory.

You use the include keyword, followed by the path to your subproject's directory. Each subproject usually resides in its own folder.

/* settings.gradle */
rootProject.name = 'my-multi-project'

include 'app'
include 'library'

Subproject Directory Structure

Once declared in settings.gradle, your project structure will typically look like this:

my-multi-project/ (root project)
- settings.gradle
- build.gradle (root build file)
- app/ (subproject 1)
  - build.gradle
  - ... (source code, resources)
- library/ (subproject 2)
  - build.gradle
  - ... (source code, resources)

Each subproject gets its own build.gradle file.

Subproject Build Files

Just like your root project, each subproject has its own build.gradle file. This allows you to define specific configurations, dependencies, and tasks for that particular module.

For example, your app subproject might build a runnable application, while your library subproject might produce a reusable JAR.

/* library/build.gradle */
plugins {
    id 'java'
}

group 'com.coddykit'
version '1.0-SNAPSHOT'

repositories {
    mavenCentral()
}

dependencies {
    testImplementation platform('org.junit:junit-bom:5.9.1')
    testImplementation 'org.junit.jupiter:junit-jupiter'
}

Defining a Subproject Task

You can define tasks within a subproject's build.gradle file. These tasks are then specific to that subproject.

Let's add a simple task to our library subproject that prints a message.

/* library/build.gradle */
plugins {
    id 'java'
}

group 'com.coddykit'
version '1.0-SNAPSHOT'

repositories {
    mavenCentral()
}

task helloLibrary {
    doLast {
        println "Hello from the Library subproject!"
    }
}

Executing Subproject Tasks

To run a task belonging to a specific subproject from the root directory, you use a colon : to separate the subproject name and the task name.

For example, to run the helloLibrary task from our library subproject:

public class Main {
  public static void main(String[] args) {
    System.out.println("To run the task: gradle :library:helloLibrary");
    System.out.println("Output will be: Hello from the Library subproject!");
  }
}

Common Configuration: allprojects

Sometimes, you want to apply the same configuration to all projects in your multi-project build (the root project and all its subprojects).

You can do this using the allprojects { ... } block in your root build.gradle file.

/* build.gradle (root) */

allprojects {
    group 'com.coddykit.common'
    version '1.0.0'

    repositories {
        mavenCentral()
    }
}

Targeting Specific Subprojects

While allprojects is great for common settings, you often need to configure individual subprojects from the root build file.

You can use the project(':subprojectName') { ... } block to apply configuration specifically to one subproject.

/* build.gradle (root) */

project(':app') {
    apply plugin: 'application'
    mainClassName = 'com.coddykit.app.MainApp'
}

project(':library') {
    apply plugin: 'java-library'
}

Sharing Properties

You can also share properties or variables from your root project to all subprojects. This is useful for things like consistent version numbers or build flags.

Use the ext block (for "extra properties") in the root build.gradle and access it with rootProject.ext.propertyName in subprojects.

/* build.gradle (root) */
ext {
    groovyVersion = '3.0.9'
    springBootVersion = '2.7.5'
}

allprojects {
    // Access properties in subprojects
    println "Groovy Version: ${rootProject.ext.groovyVersion}"
}

Multi-Select Check

Which of the following statements about Gradle subprojects and their configuration are TRUE?

Subprojects Recap

Great job! You've learned the basics of setting up and configuring Gradle subprojects.

Subprojects help organize large builds.
They are declared in settings.gradle using include.
Each subproject has its own build.gradle.
You can configure all projects using allprojects { ... } or specific ones using project(':name') { ... }.
Tasks are run with the :subproject:task syntax.

Next, we'll explore how subprojects can depend on each other!

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Subproyek & Konfigurasi” gratis?

Ya — teks lengkap “Subproyek & Konfigurasi” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Groovy & Gradle: JVM Automation and Build Engineering, upgrade ke CoddyKit PRO. Kursus Groovy & Gradle: JVM Automation and Build Engineering mencakup 4 pelajaran total.

Apa yang akan aku pelajari di “Subproyek & Konfigurasi”?

Definisikan dan konfigurasikan subproyek, serta pahami cara subproyek berinteraksi dalam pembangunan multi-proyek. Kamu berlatih Groovy & Gradle: JVM Automation and Build Engineering dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.

Apakah aku perlu pengalaman untuk memulai Groovy & Gradle: JVM Automation and Build Engineering?

Tidak diperlukan pengalaman sebelumnya. Groovy & Gradle: JVM Automation and Build Engineering di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 2 dari 4.

Berapa lama pelajaran “Subproyek & Konfigurasi” memakan waktu?

Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.

Bisakah aku menulis dan menjalankan kode dalam pelajaran Groovy & Gradle: JVM Automation and Build Engineering ini?

Ya. Setiap pelajaran Groovy & Gradle: JVM Automation and Build Engineering menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.

Semua pelajaran dalam kursus ini

← Kembali ke Groovy & Gradle: JVM Automation and Build Engineering