Estrutura de projetos Gradle

A well-organized project is key to successful development! Just like a recipe needs clear steps, a software project needs a clear structure.

Gradle projects follow a standard layout. This makes it easier for developers to understand, maintain, and collaborate on code.

Every Gradle build has a root project. This is usually the top-level directory where you run Gradle commands.

• It's the starting point for Gradle's build process.
• It can be a single project or contain multiple subprojects.

Think of it as the main folder for your entire application.

The settings.gradle file is crucial for telling Gradle about your project structure.

• It defines the project's name.
• For multi-project builds, it lists all subprojects.

Even for a single project, it's good practice to have this file.

The build.gradle file is where you define all the rules for building your project. It contains:

• Plugins to add specific functionalities (like Java compilation).
• Project dependencies (libraries your code needs).
• Custom tasks and configurations.

This is your project's main instruction manual for Gradle!

When you initialize a Gradle project, you'll see a few important files:

• settings.gradle: Configures the build structure.
• build.gradle: Defines build logic (tasks, dependencies).
• gradlew (and gradlew.bat): The Gradle Wrapper scripts.
• .gradle/: Directory for Gradle's internal files (cache, daemon logs).

These files work together to make your build happen.

Gradle projects typically follow a convention for directories:

• src/: Contains all your source code and resources.
• build/: Where Gradle puts all generated files (compiled code, JARs, reports).
• lib/ (optional): Sometimes used for unmanaged, local dependencies.

Sticking to this layout helps Gradle find things automatically.

The src directory is further organized:

• src/main/java: Your main application's Java source files.
• src/main/resources: Non-code assets for your main app (e.g., config files).
• src/test/java: Your test source files.
• src/test/resources: Non-code assets for your tests.

This separation helps keep your code clean and manageable.

Here's a simple build.gradle file for a Java project. It tells Gradle to apply the Java plugin and define basic project info.

Let's create a simple Java program that fits into our src/main/java structure. Try running it!

When you run a Gradle command (like gradle build), here's a simplified flow:

• Gradle finds and executes settings.gradle.
• It then processes the build.gradle file(s).
• Plugins are applied, tasks are configured.
• Finally, the requested tasks are executed (e.g., compile code, run tests).

This process transforms your source code into a usable output.

In this lesson, we explored the standard structure of a Gradle project:

• The root project as the entry point.
• settings.gradle for project configuration.
• build.gradle for core build logic.
• The conventional src/ and build/ directories.

This structure ensures clarity and efficiency in your build automation. Next, we'll dive deeper into tasks!