gradle-reference

To set up a Gradle multi-module project, you need a root build configuration with settings.gradle.kts to include modules, a libs.versions.toml version catalog, and per-module build.gradle.kts files to standardize the build scripts across the project.

The best way to manage dependencies across multiple Gradle modules is by using a centralized version catalog file named libs.versions.toml, which standardizes dependency declarations and build settings across all included modules.

Yes, this Gradle template works for both Java and Kotlin projects. It provides a standardized module structure, version catalogs, and build scripts that are applicable for bootstrapping new and existing codebases in either language.

To add a new module to a Gradle multi-module build, you create a per-module build.gradle.kts file using the template reference and then apply a strategy to include the new module's path within the root settings.gradle.kts file.

You need a version catalog in your Gradle build when you want to enforce consistent dependency declarations and standardized build configurations across many modules in a multi-module project setup.

Bootstrapping a consistent Gradle multi-module build requires a root settings.gradle.kts, a libs.versions.toml version catalog, and standardized per-module build.gradle.kts templates to unify the project structure.