maven-dependency-update

Align Maven pom.xml dependencies with the Quarkus BOM.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/baldimir/bob-skills --skill maven-dependency-update-baldimir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maven-dependency-update
Source: https://github.com/baldimir/bob-skills/tree/main/.bob/skills/maven-dependency-update
Command: npx skills add https://github.com/baldimir/bob-skills --skill maven-dependency-update-baldimir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maven dependency drift is eliminated by aligning project pom.xml dependencies with the Quarkus BOM, ensuring consistent versions across modules.

Core Features & Use Cases

  • BOM-first dependency management: never specify a version for BOM-managed artifacts; rely on the BOM to resolve versions.
  • Safe upgrade workflow: validates compatibility with the Quarkus platform before proposing upgrades and requires explicit user confirmation before applying changes.
  • Drift detection and remediation: detects explicit version overrides and suggests BOM-aligned changes, including ADR for major upgrades when necessary.

Quick Start

Propose and apply BOM-aligned dependency updates for a Quarkus-based project.

Frequently Asked Questions about maven-dependency-update

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

FAQPage Schema
How do I align Maven dependencies with the Quarkus BOM?

To align Maven dependencies with the Quarkus BOM, the Skill detects explicit version overrides in your pom.xml, enforces BOM-first rules, and suggests BOM-aligned changes after validating compatibility with the Quarkus platform.

What is BOM-first dependency management in Quarkus?

BOM-first dependency management in Quarkus means never specifying a version for BOM-managed artifacts. You rely entirely on the Quarkus BOM to resolve versions, ensuring consistent dependencies across multi-module builds.

How do I upgrade Quarkus without causing dependency drift?

To upgrade Quarkus safely without dependency drift, the Skill validates compatibility with the Quarkus platform before proposing upgrades and requires explicit user confirmation before applying changes to your pom.xml.

Can I use this to fix explicit version overrides in a multi-module Maven build?

Yes, you can use this to fix explicit version overrides in multi-module Maven builds. The Skill detects drift across Quarkus-flow projects, suggests BOM-aligned changes, and can generate an ADR for major upgrades.

Why does the Quarkus BOM forbid explicit version overrides in pom.xml?

The Quarkus BOM forbids explicit version overrides in pom.xml to prevent dependency drift. Enforcing this rule ensures consistent versions across modules and validates compatibility with the Quarkus platform.