This is an automated email from the ASF dual-hosted git repository.
hboutemy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-dependency-plugin.git
The following commit(s) were added to refs/heads/master by this push:
new 5e78508 reordered goals
5e78508 is described below
commit 5e78508fa1d5a9a87cecfcb21ba9e91a5944f39e
Author: Hervé Boutemy <[email protected]>
AuthorDate: Wed Jul 24 20:28:22 2019 +0200
reordered goals
---
src/site/apt/usage.apt.vm | 170 ++++++++++++++++++++++++----------------------
1 file changed, 88 insertions(+), 82 deletions(-)
diff --git a/src/site/apt/usage.apt.vm b/src/site/apt/usage.apt.vm
index 20d729f..0ccbea4 100644
--- a/src/site/apt/usage.apt.vm
+++ b/src/site/apt/usage.apt.vm
@@ -508,64 +508,6 @@ mvn dependency:purge-local-repository
-DresolutionFuzziness=artifactId
correct resolution.
-* <<<dependency:build-classpath>>>
-
- Since: 2.0-alpha-2
-
- This goal will output a classpath string of dependencies from the local
repository to a file or log and optionally attach and deploy the file. For
instance, the file would contain a classpath string like this:
-
-+---+
-/home/foo/.m2/repository/org/java/utils/util/util-1.0.jar:/home/foo/.m2/ ....
-+---+
-
- The resulting file could then be used like this:
-
-+---+
-java -cp `cat resultFile` MyClass
-+---+
-
- In its simplest form, to output the classpath to the log, the goal can be
called like this:
-
-+---+
-mvn dependency:build-classpath
-+---+
-
- or to write the classpath to cp.txt.:
-
-+---+
-mvn dependency:build-classpath -Dmdep.outputFile=cp.txt
-+---+
-
- The goal can also be bound to a lifecycle phase with the following
configuration:
-
-+---+
-<project>
- [...]
- <build>
- <plugins>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-dependency-plugin</artifactId>
- <version>${project.version}</version>
- <executions>
- <execution>
- <id>build-classpath</id>
- <phase>generate-sources</phase>
- <goals>
- <goal>build-classpath</goal>
- </goals>
- <configuration>
- <!-- configure the plugin here -->
- </configuration>
- </execution>
- </executions>
- </plugin>
- </plugins>
- </build>
- [...]
-</project>
-+---+
-
* <<<dependency:analyze>>>
This goal performs byte code analysis to determine missing or unused
dependencies. This goal is meant to be launched from the command line. It will
fork the build and execute test-compile so there are class files to analyze.
@@ -586,6 +528,7 @@ mvn dependency:analyze
[WARNING] org.apache.maven.shared:maven-invoker:jar:2.0.7-SNAPSHOT:test
+---+
+
* <<<dependency:analyze-dep-mgt>>>
This goal looks at the dependencies after final resolution and looks for
mismatches in your dependencyManagement section.
@@ -619,6 +562,32 @@ mvn dependency:analyze-dep-mgt
[WARNING] Potential problems found in Dependency Management
+---+
+
+* <<<dependency:analyze-report>>>
+
+ This goal is used to include a report of the dependencies in the output of
the <<<maven-site-plugin>>>.
+
++-------+
+ <reporting>
+ <plugins>
+ ...
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-dependency-plugin</artifactId>
+ <version>${project.version}</version>
+ <reportSets>
+ <reportSet>
+ <reports>
+ <report>analyze-report</report>
+ </reports>
+ </reportSet>
+ </reportSets>
+ </plugin>
+ </plugins>
+ </reporting>
++-------+
+
+
* <<<dependency:tree>>>
This goal is used to view the dependency hierarchy of the project currently
being built.
@@ -653,11 +622,72 @@ mvn dependency:tree -Doutput=/path/to/file
mvn dependency:tree -Doutput=/path/to/file.graphml -DoutputType=graphml
+-----+
+
+* <<<dependency:build-classpath>>>
+
+ Since: 2.0-alpha-2
+
+ This goal will output a classpath string of dependencies from the local
repository to a file or log and optionally attach and deploy the file. For
instance, the file would contain a classpath string like this:
+
++---+
+/home/foo/.m2/repository/org/java/utils/util/util-1.0.jar:/home/foo/.m2/ ....
++---+
+
+ The resulting file could then be used like this:
+
++---+
+java -cp `cat resultFile` MyClass
++---+
+
+ In its simplest form, to output the classpath to the log, the goal can be
called like this:
+
++---+
+mvn dependency:build-classpath
++---+
+
+ or to write the classpath to cp.txt.:
+
++---+
+mvn dependency:build-classpath -Dmdep.outputFile=cp.txt
++---+
+
+ The goal can also be bound to a lifecycle phase with the following
configuration:
+
++---+
+<project>
+ [...]
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-dependency-plugin</artifactId>
+ <version>${project.version}</version>
+ <executions>
+ <execution>
+ <id>build-classpath</id>
+ <phase>generate-sources</phase>
+ <goals>
+ <goal>build-classpath</goal>
+ </goals>
+ <configuration>
+ <!-- configure the plugin here -->
+ </configuration>
+ </execution>
+ </executions>
+ </plugin>
+ </plugins>
+ </build>
+ [...]
+</project>
++---+
+
+
* <<<dependency:list-repositories>>>
This goal is used to list all the repositories that this build depends upon.
It will show repositories defined in your settings,
poms and declared in transitive dependency poms.
+
* <<<dependency:get>>>
This goal is used to fetch an artifact and (optionally) its dependencies
from remote repositories using its Maven coordinates.
@@ -667,27 +697,3 @@ mvn dependency:get -DgroupId=org.apache.maven
-DartifactId=maven-core -Dversion=
mvn dependency:get -DgroupId=org.apache.maven -DartifactId=maven-core
-Dversion=2.2.1 -Dpackaging=jar -Dclassifier=sources
-DremoteRepositories=http://repo1.maven.apache.org/maven2
mvn dependency:get -Dartifact=org.apache.maven:maven-core:2.2.1:jar:sources
-DremoteRepositories=http://repo1.maven.apache.org/maven2 -Ddest=/tmp/myfile.jar
+-----+
-
-* <<<dependency:analyze-report>>> Report
-
- This goal is used to include a report of the dependencies in the output of
the <<<maven-site-plugin>>>.
-
-+-------+
- <reporting>
- <plugins>
- ...
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-dependency-plugin</artifactId>
- <version>${project.version}</version>
- <reportSets>
- <reportSet>
- <reports>
- <report>analyze-report</report>
- </reports>
- </reportSet>
- </reportSets>
- </plugin>
- </plugins>
- </reporting>
-+-------+
\ No newline at end of file
