子项目与配置
定义和配置子项目，了解它们如何在多项目构建中相互协作。
子项目与配置 是 CoddyKit 上的免费 Groovy & Gradle: JVM Automation and Build Engineering 课时。 这是第 2 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Groovy & Gradle: JVM Automation and Build Engineering 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Groovy & Gradle: JVM Automation and Build Engineering 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
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.gradlebuild.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.gradleusinginclude. - Each subproject has its own
build.gradle. - You can configure all projects using
allprojects { ... }or specific ones usingproject(':name') { ... }. - Tasks are run with the
:subproject:tasksyntax.
Next, we'll explore how subprojects can depend on each other!
用 AI 导师学习 Groovy — 免费
在浏览器中编写并运行真实代码，获得全天候 AI 导师的即时帮助，并在网页或应用中继续学习。
- 课程
- 12
- 课程
- 48
常见问题解答
「子项目与配置」课时是免费的吗？
是的 — 「子项目与配置」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Groovy & Gradle: JVM Automation and Build Engineering 课程的其余内容，请升级到 CoddyKit PRO。 Groovy & Gradle: JVM Automation and Build Engineering 课程共包含 4 节课。
「子项目与配置」这节课中我会学到什么？
定义和配置子项目，了解它们如何在多项目构建中相互协作。 你通过在浏览器中直接运行的动手代码来练习 Groovy & Gradle: JVM Automation and Build Engineering，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 Groovy & Gradle: JVM Automation and Build Engineering 需要有经验吗？
无需任何先前经验。CoddyKit 上的 Groovy & Gradle: JVM Automation and Build Engineering 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 2 节课，共 4 节。
「子项目与配置」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 Groovy & Gradle: JVM Automation and Build Engineering 课中编写并运行代码吗？
能。每节 Groovy & Gradle: JVM Automation and Build Engineering 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。