How does the module merging process occur in the Gradle build system when working with multi-module projects?

In Gradle, a multi-module project consists of several modules (subprojects), each with its own build.gradle file. The process of combining modules occurs at the root project level, where all modules are listed in settings.gradle (or settings.gradle.kts).

During build:

• Configuration of all modules is loaded first.
• Gradle builds a dependency graph between modules.
• Modules can depend on each other, and these dependencies are specified in build.gradle via implementation project(':moduleName').
• Gradle considers these dependencies and builds modules in the correct order.

As a result, a single artifact (e.g., APK or library) is produced, which includes all necessary modules and their dependencies.

Thus, module aggregation is the process of resolving dependencies and sequentially building all parts of the project within a single Gradle build session.