dependency-management

Name: dependency-management
Availability: InStock
Author: Bitso

Manage Java/Gradle dependency versions via version catalogs and BOMs.

40|33|Updated Aug 20, 2015

Search Tags:#dependencies #build #gradle #version catalog #versions #bom

Ready to run

npx skills add https://github.com/bitsoex/bitso-java --skill dependency-management-bitsoex

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dependency-management
Source: https://github.com/bitsoex/bitso-java/tree/main/.claude/skills/dependency-management
Command: npx skills add https://github.com/bitsoex/bitso-java --skill dependency-management-bitsoex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a robust strategy for managing library versions, resolving conflicts, and ensuring consistency across Java/Gradle projects, preventing dependency hell.

Core Features & Use Cases

Version Centralization: Enforces all dependency versions in gradle/libs.versions.toml.
BOM Management: Utilizes Bill of Materials for consistent transitive dependency versions.
Bundle Patterns: Simplifies build files by grouping related dependencies.
Use Case: When adding a new library or upgrading existing ones, this Skill ensures versions are managed centrally, preventing conflicts and simplifying maintenance.

Quick Start

Apply the dependency management skill to centralize all versions in the gradle/libs.versions.toml file.

Frequently Asked Questions about dependency-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I centralize Gradle dependency versions in a Java project?▼

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.

What is a BOM in Gradle and when should I use it?▼

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.

Does this dependency management strategy support Gradle 8.x and 9.x?▼

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.

How do I group related dependencies using bundle patterns in Gradle?▼

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.

What's the best way to prevent dependency conflicts when upgrading libraries in Gradle?▼

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.

Why does my Gradle build pull in unexpected transitive dependency versions?▼

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.