Dependency Tree & Analysis
About
A dependency tree in Maven is a hierarchical representation of all dependencies in a project, including direct and transitive dependencies. It helps to -
Identify dependency conflicts (duplicate or incompatible versions).
Understand why a dependency is included in the project.
Optimize dependency versions to avoid unnecessary bloating.
Example of a Dependency Tree
Consider the following pom.xml:
When you run the following command:
We will get output like this:
Notice that log4j-core appears twice—once as direct and once as transitive (from spring-boot-starter).
Maven will use the nearest version (2.17.1 in this case).
Dependency Tree Components
1. Direct Dependencies
These are explicitly declared in
pom.xml.Example:
spring-boot-starter-webandlog4j-coreare direct dependencies.
2. Transitive Dependencies
These are indirect dependencies pulled in by other dependencies.
Example:
spring-boot-starter-webpulls inlog4j-core.
3. Conflict Resolution
When different versions of a library exist, Maven applies Nearest-Wins Strategy.
Commands for Analyzing Dependencies
1. Checking Full Dependency Tree
Displays all dependencies, including transitive ones.
2. Finding Why a Dependency Exists
This command shows which dependencies brought in log4j-core.
3. Displaying Dependencies in a Graphical Format
For better readability, generate a dependency graph:
Then use a tool like Graphviz to visualize it.
4. Checking Dependency Versions
Lists resolved versions of all dependencies.
5. Finding Dependency Conflicts
Shows conflicts and which version Maven picks.
Last updated
Was this helpful?