Subproyectos y configuraciones

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.

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.

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.

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.

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.

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:

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.

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.

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.

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!