Note that the mvn dependency:tree command would typically process all pom.xml in the codebase at once, and would generate one tree for each each pom.xml
a good set of args to run the command would be : mvn dependency:tree -DoutputFile=maven-dependency-tree.lock -DoutputType=graphml and optionally with-Dmaven.test.skip=true and -DskipTests to skip tests, or various other options (such as scope) to filter the tree. See https://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.html
As a follow up to:
Here are the next candidates:
mvn dependency:treecommand would typically process all pom.xml in the codebase at once, and would generate one tree for each each pom.xmlmvn dependency:tree -DoutputFile=maven-dependency-tree.lock -DoutputType=graphmland optionally with-Dmaven.test.skip=trueand-DskipTeststo skip tests, or various other options (such as scope) to filter the tree. See https://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.htmlcomposerbundlergo(though this should be standard by now)