Author: hboutemy
Date: Wed Aug 1 20:56:35 2012
New Revision: 1368245
URL: http://svn.apache.org/viewvc?rev=1368245&view=rev
Log:
fixed links
Modified:
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copying-artifacts.apt.vm
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/failing-the-build-on-dependency-analysis-warnings.apt.vm
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/filtering-the-dependency-tree.apt
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/preparing-dependencies.apt
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/resolving-conflicts-using-the-dependency-tree.apt
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/unpacking-artifacts.apt.vm
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/unpacking-project-dependencies.apt.vm
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/using-dependencies-sources.apt.vm
Modified:
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copying-artifacts.apt.vm
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copying-artifacts.apt.vm?rev=1368245&r1=1368244&r2=1368245&view=diff
==============================================================================
---
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copying-artifacts.apt.vm
(original)
+++
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copying-artifacts.apt.vm
Wed Aug 1 20:56:35 2012
@@ -180,16 +180,16 @@ Copying specific artifacts
</project>
+---+
-{Using an alternate local repository}:
+{Using an alternate local repository}
<<dependency:copy>> always downloads artifacts to default local repository
first, and then
copy the artifacts to the desired locations. For large size unique
snapshot artifacts, the downloads can quickly
fill up default local repository, and therefore local disk, after many
executions.
To clean up the downloaded artifacts as part the build, set
<localRepositoryDirectory>'s value
to a location in your project's target directory.
-
+
This use case also applies to <<dependency:unpack>> goal.
-
+
+---+
<project>
[...]
@@ -222,10 +222,10 @@ Copying specific artifacts
</build>
[...]
</project>
-+---+
-
-{Copying from the command line}:
-
++---+
+
+{Copying from the command line}
+
If you intend to configure this mojo for execution on the command line
using:
+---+
@@ -233,7 +233,7 @@ mvn dependency:copy
+---+
you must not put the configuration inside the <executions> tag. Your
configuration should look like this:
-
+
+---+
<project>
[...]
@@ -262,4 +262,4 @@ mvn dependency:copy
</build>
[...]
</project>
-+---+
++---+
Modified:
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/failing-the-build-on-dependency-analysis-warnings.apt.vm
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/failing-the-build-on-dependency-analysis-warnings.apt.vm?rev=1368245&r1=1368244&r2=1368245&view=diff
==============================================================================
---
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/failing-the-build-on-dependency-analysis-warnings.apt.vm
(original)
+++
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/failing-the-build-on-dependency-analysis-warnings.apt.vm
Wed Aug 1 20:56:35 2012
@@ -25,10 +25,10 @@
Failing the build on dependency analysis warnings
- A project's dependencies can be analyzed as part of the build process
by binding the <<<dependency:analyze-only>>>
- goal to the lifecycle. By default, the analysis will be performed
during the <<<verify>>> lifecycle phase. The
- plugin can then be configured to fail the build if any dependency
analysis warnings are encountered by setting the
- <<<failOnWarning>>> parameter. See the following POM configuration for
an example:
+ A project's dependencies can be analyzed as part of the build process by
binding the <<<dependency:analyze-only>>>
+ goal to the lifecycle. By default, the analysis will be performed during
the <<<verify>>> lifecycle phase. The
+ plugin can then be configured to fail the build if any dependency analysis
warnings are encountered by setting the
+ <<<failOnWarning>>> parameter. See the following POM configuration for an
example:
+---+
<project>
@@ -57,12 +57,12 @@ Failing the build on dependency analysis
</project>
+---+
- Note that the <<<dependency:analyze-only>>> goal is used in preference
to <<<dependency:analyze>>> since it doesn't
- force a further compilation of the project, but uses the compiled
classes produced from the earlier
- <<<test-compile>>> phase in the lifecycle.
+ Note that the <<<dependency:analyze-only>>> goal is used in preference to
<<<dependency:analyze>>> since it doesn't
+ force a further compilation of the project, but uses the compiled classes
produced from the earlier
+ <<<test-compile>>> phase in the lifecycle.
- The project's dependencies will then be automatically analyzed during
the <<<verify>>> lifecycle phase, which can be
- executed explicitly as follows:
+ The project's dependencies will then be automatically analyzed during the
<<<verify>>> lifecycle phase, which can be
+ executed explicitly as follows:
+---+
mvn verify
Modified:
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/filtering-the-dependency-tree.apt
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/filtering-the-dependency-tree.apt?rev=1368245&r1=1368244&r2=1368245&view=diff
==============================================================================
---
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/filtering-the-dependency-tree.apt
(original)
+++
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/filtering-the-dependency-tree.apt
Wed Aug 1 20:56:35 2012
@@ -25,15 +25,15 @@
Filtering the dependency tree
- A project's dependency tree can be filtered to locate specific
dependencies. For example, to find out why Velocity
- is being used by the Maven Dependency Plugin, we can execute the
following in the project's directory:
+ A project's dependency tree can be filtered to locate specific dependencies.
For example, to find out why Velocity
+ is being used by the Maven Dependency Plugin, we can execute the following
in the project's directory:
+---+
mvn dependency:tree -Dincludes=velocity:velocity
+---+
- Which outputs:
-
+ Which outputs:
+
+---+
[INFO] [dependency:tree]
[INFO]
org.apache.maven.plugins:maven-dependency-plugin:maven-plugin:2.0-alpha-5-SNAPSHOT
@@ -42,27 +42,27 @@ mvn dependency:tree -Dincludes=velocity:
[INFO] \- velocity:velocity:jar:1.4:compile
+---+
- Thus we can see that Velocity is being brought in by Plexus Velocity,
which in turn is being brought in by a direct
- dependency on Doxia Site Renderer.
+ Thus we can see that Velocity is being brought in by Plexus Velocity, which
in turn is being brought in by a direct
+ dependency on Doxia Site Renderer.
* Filter pattern syntax
- The syntax for filter patterns is as follows:
+ The syntax for filter patterns is as follows:
+---+
[groupId]:[artifactId]:[type]:[version]
+---+
- Where each pattern segment is optional and supports full and partial
<<<*>>> wildcards. An empty pattern segment is
- treated as an implicit wildcard.
+ Where each pattern segment is optional and supports full and partial <<<*>>>
wildcards. An empty pattern segment is
+ treated as an implicit wildcard.
- For example, <<<org.apache.*>>> would match all artifacts whose group
id started with <<<org.apache.>>>, and
- <<<:::*-SNAPSHOT>>> would match all snapshot artifacts.
+ For example, <<<org.apache.*>>> would match all artifacts whose group id
started with <<<org.apache.>>>, and
+ <<<:::*-SNAPSHOT>>> would match all snapshot artifacts.
* Excluding dependencies from the tree
- The dependency tree can also be filtered to remove specific
dependencies. For example, to exclude Plexus
- dependencies from the tree, we can execute the following:
+ The dependency tree can also be filtered to remove specific dependencies.
For example, to exclude Plexus
+ dependencies from the tree, we can execute the following:
+---+
mvn dependency:tree -Dexcludes=org.codehaus.plexus
@@ -70,8 +70,8 @@ mvn dependency:tree -Dexcludes=org.codeh
* Specifying multiple patterns
- Multiple patterns can be specified when filtering the dependency tree
by separating the patterns with commas. For
- example, to exclude Maven and Plexus dependencies from the tree, we can
execute the following:
+ Multiple patterns can be specified when filtering the dependency tree by
separating the patterns with commas. For
+ example, to exclude Maven and Plexus dependencies from the tree, we can
execute the following:
+---+
mvn dependency:tree -Dexcludes=org.apache.maven*,org.codehaus.plexus
@@ -79,8 +79,8 @@ mvn dependency:tree -Dexcludes=org.apach
* Including and excluding dependencies from the tree
- Both include and exclude patterns and be specified together to filter
the dependency tree. For example, to locate
- all non-snapshot Plexus dependencies in the tree, we can execute the
following:
+ Both include and exclude patterns and be specified together to filter the
dependency tree. For example, to locate
+ all non-snapshot Plexus dependencies in the tree, we can execute the
following:
+---+
mvn dependency:tree -Dincludes=org.codehaus.plexus -Dexcludes=:::*-SNAPSHOT
Modified:
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/preparing-dependencies.apt
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/preparing-dependencies.apt?rev=1368245&r1=1368244&r2=1368245&view=diff
==============================================================================
---
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/preparing-dependencies.apt
(original)
+++
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/preparing-dependencies.apt
Wed Aug 1 20:56:35 2012
@@ -23,11 +23,14 @@
Mar 2007
------
-How to prepare your dependencies before updating to Maven 2.0.6:
+How to prepare your dependencies before updating to Maven 2.0.6
- If you have dependencies in dependencyManagement that conflict with
transitive dependencies, the fix for MNG-1577 may alter the version you get
when running a build with 2.0.6. To ensure a smooth transition, there is a tool
to detect these conditions.
+ If you have dependencies in dependencyManagement that conflict with
transitive dependencies,
+ the fix for MNG-1577 may alter the version you get when running a build with
2.0.6.
+ To ensure a smooth transition, there is a tool to detect these conditions.
- In your project, run "mvn dependency:analyze" (be sure to use 2.0.5 or the
plugin won't detect mismatches) This will display output similar to below:
+ In your project, run <<<mvn dependency:analyze>>> (be sure to use 2.0.5 or
the plugin won't detect mismatches).
+ This will display output similar to below:
+---+
[INFO] [dependency:analyze]
Modified:
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/resolving-conflicts-using-the-dependency-tree.apt
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/resolving-conflicts-using-the-dependency-tree.apt?rev=1368245&r1=1368244&r2=1368245&view=diff
==============================================================================
---
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/resolving-conflicts-using-the-dependency-tree.apt
(original)
+++
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/resolving-conflicts-using-the-dependency-tree.apt
Wed Aug 1 20:56:35 2012
@@ -25,16 +25,16 @@
Resolving conflicts using the dependency tree
- A project's dependency tree can be expanded to display dependency
conflicts. For example, to find out why Commons
- Collections 2.0 is being used by the Maven Dependency Plugin, we can
execute the following in the project's
- directory:
+ A project's dependency tree can be expanded to display dependency conflicts.
For example, to find out why Commons
+ Collections 2.0 is being used by the Maven Dependency Plugin, we can execute
the following in the project's
+ directory:
+---+
mvn dependency:tree -Dverbose -Dincludes=commons-collections
+---+
- The <<<verbose>>> flag instructs the dependency tree to display
conflicting dependencies that were omitted from the
- resolved dependency tree. In this case, the goal outputs:
+ The <<<verbose>>> flag instructs the dependency tree to display conflicting
dependencies that were omitted from the
+ resolved dependency tree. In this case, the goal outputs:
+---+
[INFO] [dependency:tree]
@@ -48,8 +48,8 @@ mvn dependency:tree -Dverbose -Dincludes
[INFO] \- commons-collections:commons-collections:jar:2.0:compile
+---+
- Thus we can see that Commons Collections 2.0 was chosen over 2.1 since
it is nearer, and by default Maven resolves
- version conflicts with a nearest-wins strategy.
+ Thus we can see that Commons Collections 2.0 was chosen over 2.1 since it is
nearer, and by default Maven resolves
+ version conflicts with a nearest-wins strategy.
- More specifically, in verbose mode the dependency tree shows
dependencies that were omitted for: being a duplicate
- of another; conflicting with another's version and/or scope; and
introducing a cycle into the dependency tree.
\ No newline at end of file
+ More specifically, in verbose mode the dependency tree shows dependencies
that were omitted for: being a duplicate
+ of another; conflicting with another's version and/or scope; and introducing
a cycle into the dependency tree.
Modified:
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/unpacking-artifacts.apt.vm
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/unpacking-artifacts.apt.vm?rev=1368245&r1=1368244&r2=1368245&view=diff
==============================================================================
---
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/unpacking-artifacts.apt.vm
(original)
+++
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/unpacking-artifacts.apt.vm
Wed Aug 1 20:56:35 2012
@@ -26,7 +26,7 @@
Unpacking specific artifacts
- This is pretty similar to the {{{copying-artifacts.html}Copying Specific
Artifacts}}
+ This is pretty similar to the {{{./copying-artifacts.html}Copying Specific
Artifacts}}
example. The difference is that instead of copying the artifacts, they are
unpacked.
To unpack the copied artifacts, use the <<<dependency:unpack>>> mojo and
configure the plugin into something like the sample below:
@@ -121,9 +121,3 @@ mvn dependency:unpack
[...]
</project>
+---+
-
-
-
-
-
-
Modified:
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/unpacking-project-dependencies.apt.vm
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/unpacking-project-dependencies.apt.vm?rev=1368245&r1=1368244&r2=1368245&view=diff
==============================================================================
---
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/unpacking-project-dependencies.apt.vm
(original)
+++
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/unpacking-project-dependencies.apt.vm
Wed Aug 1 20:56:35 2012
@@ -26,7 +26,7 @@
Unpacking project dependencies
- This is pretty similar to the {{{copying-project-dependencies.html}Copying
direct dependencies}}
+ This is pretty similar to the {{{./copying-project-dependencies.html}Copying
direct dependencies}}
example. The difference is that the direct dependencies are unpacked,
including the transitive dependencies. To unpack the artifacts, use the
<<<dependency:unpack-dependencies>>> mojo and configure the dependency plugin
@@ -63,7 +63,3 @@ Unpacking project dependencies
[...]
</project>
+---+
-
-
-
-
Modified:
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/using-dependencies-sources.apt.vm
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/using-dependencies-sources.apt.vm?rev=1368245&r1=1368244&r2=1368245&view=diff
==============================================================================
---
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/using-dependencies-sources.apt.vm
(original)
+++
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/using-dependencies-sources.apt.vm
Wed Aug 1 20:56:35 2012
@@ -25,8 +25,8 @@
Using project dependencies' sources
- This is pretty similar to the {{{copying-project-dependencies.html}Copying
project dependencies}}
- or {{{unpacking-project-dependencies.html}Unpacking project dependencies}}
+ This is pretty similar to the {{{./copying-project-dependencies.html}Copying
project dependencies}}
+ or {{{./unpacking-project-dependencies.html}Unpacking project dependencies}}
examples.
Instead of using the project dependencies it uses their sources. Use the
goal
@@ -64,7 +64,3 @@ Using project dependencies' sources
[...]
</project>
+---+
-
-
-
-
