dependency-management

You can centralize Gradle dependency versions by defining all library references in a version catalog file located at gradle/libs.versions.toml. This approach prevents dependency hell by enforcing consistent versioning across all modules in the project.

A BOM, or Bill of Materials, is a special dependency that provides consistent transitive dependency versions across a project. Use a BOM in Gradle when you need to align versions of related libraries without explicitly declaring each version individually in your build files.

Yes, this dependency management strategy supports Gradle 8.x and 9.x environments. It provides version centralization, never-downgrade policies, and resolution strategies specifically designed to work within these modern Gradle versions.

You group related dependencies using bundle patterns by defining them within your version catalog. This simplifies your build files by allowing you to include multiple coordinated libraries through a single bundle reference rather than declaring each dependency separately.

The best way to prevent dependency conflicts during upgrades is to enforce versions centrally using a version catalog and BOMs. Applying never-downgrade policies and resolution strategies ensures that transitive dependencies remain consistent and prevents version mismatches.

Unexpected transitive dependency versions often occur without centralized version management or BOMs. Applying a version catalog with explicit constraints and resolution strategies enforces consistent versions and prevents Gradle from automatically resolving conflicting transitive dependencies.