Maven dependency Plugin: Difference between revisions
Jump to navigation
Jump to search
(→Tree) |
(→Tree) |
||
Line 20: | Line 20: | ||
mvn dependency:tree | mvn dependency:tree | ||
To analyze the dependency tree for a specific group: | |||
==Build Classpath== | ==Build Classpath== |
Revision as of 22:21, 29 July 2019
External
Internal
Operations
List
mvn dependency:resolve
Tree
mvn dependency:tree
To analyze the dependency tree for a specific group:
Build Classpath
This is a goal that can be used to build a complete dependency classpath (less the artifact itself), as required by the Maven project artifact to function. The classpath is generated in the format to be used in java -cp. It proved useful in wrapper scripts, where it eliminates the need to manually specify the classpath.
Note that the artifact itself is not present on the classpath. If needed, it has to be added independently.
mvn dependency:build-classpath
More details:
Analyze
Optimize dependencies with
mvn dependency:analyze
Include Dependencies - or Some of the Dependencies - in JAR
There are situations when we want to extract some of the dependencies and bundle them with the JAR artifact. This is done using the jar plugin and the dependency plugin together, as described here: