Goals available for this plugin:
Goal | Report? | Description |
---|---|---|
dependency:analyze | No | Analyzes the dependencies of this project and determines which are:
used and declared; used and undeclared; unused and declared. This
goal is intended to be used standalone, thus it always executes the
test-compile phase - use the
dependency:analyze-only goal instead when
participating in the build lifecycle.
By default, maven-dependency-analyzer
is used to perform the analysis, with limitations due to the fact
that it works at bytecode level, but any analyzer can be plugged in
through |
dependency:analyze-dep-mgt | No | This mojo looks at the dependencies after final resolution and looks for mismatches in your dependencyManagement section. In versions of maven prior to 2.0.6, it was possible to inherit versions that didn't match your dependencyManagement. See MNG-1577 for more info. This mojo is also useful for just detecting projects that override the dependencyManagement directly. Set ignoreDirect to false to detect these otherwise normal conditions. |
dependency:analyze-duplicate | No | Analyzes the <dependencies/> and
<dependencyManagement/> tags in the
pom.xml and determines the duplicate declared
dependencies. |
dependency:analyze-only | No | Analyzes the dependencies of this project and determines which are:
used and declared; used and undeclared; unused and declared. This
goal is intended to be used in the build lifecycle, thus it assumes
that the test-compile phase has been executed - use
the dependency:analyze goal instead when running
standalone.
By default, maven-dependency-analyzer
is used to perform the analysis, with limitations due to the fact
that it works at bytecode level, but any analyzer can be plugged in
through |
dependency:analyze-report | Yes | Analyzes the dependencies of this project and produces a report that summarizes which are: used and declared; used and undeclared; unused and declared. |
dependency:build-classpath | No | This goal will output a classpath string of dependencies from the local repository to a file or log. |
dependency:collect | No | Goal that collects the project dependencies from the repository. This goal requires Maven 3.0 or higher to function because it uses "requiresDependencyCollection". This means that it lists the groupId:artifactId:version information by downloading the pom files without downloading the actual artifacts such as jar files. This is very useful when full dependency resolution might fail due to projects which haven't been built yet. It is identical to |
dependency:copy | No | Goal that copies a list of artifacts from the repository to defined locations. |
dependency:copy-dependencies | No | Goal that copies the project dependencies from the repository to a defined location. |
dependency:display-ancestors | No | Displays all ancestor POMs of the project. This may be useful in a continuous integration system where you want to know all parent poms of the project. |
dependency:get | No | Resolves a single artifact, eventually transitively, from the
specified remote repositories. Caveat: will always check the
central repository defined in the super pom. You could use a mirror
entry in your settings.xml |
dependency:go-offline | No | Goal that resolves all project dependencies, including plugins and reports and their dependencies. Brian Fox |
dependency:help | No | Display help information on maven-dependency-plugin. Call mvn dependency:help -Ddetail=true
-Dgoal=<goal-name> to display parameter details. |
dependency:list | No | Displays the list of dependencies for this project. |
dependency:list-repositories | No | Goal that resolves all project dependencies and then lists the repositories used by the build and by the transitive dependencies |
dependency:properties | No | Goal that sets a property pointing to the artifact file for each
project dependency. For each dependency (direct and transitive) a
project property will be set which follows the
groupId:artifactId:type:[classifier] form and contains
the path to the resolved artifact. |
dependency:purge-local-repository | No | When run on a project, remove the project dependencies from the local repository, and optionally re-resolve them. Outside of a project, remove the manually given dependencies. |
dependency:resolve | No | Goal that resolves the project dependencies from the repository. When using this goal while running on Java 9 the module names will be visible as well. |
dependency:resolve-plugins | No | Goal that resolves all project plugins and reports and their dependencies. |
dependency:sources | No | Goal that resolves the project source dependencies from the repository. |
dependency:tree | No | Displays the dependency tree for this project. Multiple formats are supported: text (by default), but also DOT, graphml and TGF. |
dependency:unpack | No | Goal that retrieves a list of artifacts from the repository and unpacks them in a defined location. |
dependency:unpack-dependencies | No | Goal that unpacks the project dependencies from the repository to a defined location. |
The following specifies the minimum requirements to run this Maven plugin:
Maven | 3.0 |
JDK | 1.7 |
Memory | No minimum requirement. |
Disk Space | No minimum requirement. |
You should specify the version in your project's plugin configuration:
<project> ... <build> <!-- To define the plugin version in your parent POM --> <pluginManagement> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <version>3.1.2</version> </plugin> ... </plugins> </pluginManagement> <!-- To use the plugin goals in your POM or parent POM --> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <version>3.1.2</version> </plugin> ... </plugins> </build> ... <!-- To use the report goals in your POM or parent POM --> <reporting> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <version>3.1.2</version> </plugin> ... </plugins> </reporting> ... </project>
For more information, see "Guide to Configuring Plug-ins"