Maven Transitive Dependencies and Conflict Resolution
Fast recall
Quick revision
Core answer
Whether you can diagnose dependency conflicts — a frequent source of runtime errors — and know the tools to fix them.
Using `<exclusions>` to remove a transitive dependency without declaring the desired version, which can result in a missing class at runtime instead of resolving the conflict.
Mention `mvn dependency:tree`, `mvn dependency:analyze` (detects declared-but-unused and used-but-undeclared dependencies), and the Maven Enforcer plugin's `requireUpperBoundDeps` rule to catch version downgrades.
Interview-ready guide
Interview answer
The most frustrating Maven bug is a NoSuchMethodError at runtime that never appeared during compilation. It happens when two of your dependencies pull in different versions of the same library and Maven silently picks the wrong one.
How Maven resolves conflicts
- Maven's nearest-definition-wins rule: the version declared at the shallowest depth in the dependency tree wins — a direct
- When two versions appear at the same depth, the first-declared dependency in the POM wins — simply reordering
mvn dependency:tree -Dincludes=com.fasterxml.jackson.core:jackson-databindfilters the tree to one library, immediately showing which paths pull in which versions and which one Maven selected
The canonical fixes
- Declaring the dependency directly at depth 1 wins by the nearest-definition rule — a quick fix for a single module, but
Preventing conflicts in CI
- The Maven Enforcer plugin with
requireUpperBoundDepsfails the build when a transitive dependency resolves to a version lower than the highest requested — it catches silent downgrades before they become production incidents - Run
mvn dependency:analyzeto find declared but unused dependencies and used but undeclared transitive dependencies — both categories are maintenance risks
Maven Transitive Dependencies and Conflict Resolution
Direct Answer
Maven resolves version conflicts using nearest-definition wins: the version of a transitive dependency declared at the shallowest depth in the dependency tree wins. You resolve conflicts explicitly by declaring the desired version directly in your <dependencies> (nearest win) or enforcing it via <dependencyManagement> (centralized version management).
Common Mistakes & Pitfalls
Using <exclusions> to remove a transitive dependency without declaring the desired version, which can result in a missing class at runtime instead of resolving the conflict.
Check your understanding
Answer these without looking back at the article.
- What does `mvn dependency:analyze` tell you that `mvn dependency:tree` does not?
- How does the Maven Enforcer plugin help prevent dependency conflicts?
- What is the difference between excluding a transitive dependency and using `<dependencyManagement>`?
Related interview prep categories
1Looking for a structured roadmap?
Every module on this page is also part of the full Java backend interview track.