You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by hb...@apache.org on 2012/08/01 20:59:30 UTC

svn commit: r1368196 - /maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copying-artifacts.apt.vm

Author: hboutemy
Date: Wed Aug  1 18:59:30 2012
New Revision: 1368196

URL: http://svn.apache.org/viewvc?rev=1368196&view=rev
Log:
fixed typos

Modified:
    maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copying-artifacts.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=1368196&r1=1368195&r2=1368196&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 18:59:30 2012
@@ -72,20 +72,20 @@ Copying specific artifacts
 </project>
 +---+
 
-    Then after executing <<<mvn package>>> the artifact (junit) is copied to the
-    given alternateLocation.
+    Then after executing <<<mvn package>>>, the artifact (junit) is copied to the
+    given alternate location.
 
     Artifacts are resolved from the following sources in order:
 
-      * The current reactor,
+      * the current reactor,
 
-      * The local repository,
+      * the local repository,
 
-      * The configured remote repositories.
+      * the configured remote repositories.
 
       []
 
-    If the artifact cannot be resolved from the above sources then the build
+    If the artifact cannot be resolved from the above sources then the build will fail.
 
     If the artifact is also listed as a dependency, the <<<version>>> of the <<<artifactItem>>> will default to
     the version from the <<<dependencies>>> or <<<dependencyManagement>>>, e.g.
@@ -139,8 +139,8 @@ Copying specific artifacts
 +---+
 
     The <<<dependency:copy>>> goal can also be used to copy the just built
-    artifact to a custom location if desired. It must be bound after the
-    to any phase after the package phase so that the artifact exists in the
+    artifact to a custom location if desired. <<It must be bound
+    to any phase after the package phase>> so that the artifact exists in the
     repository. The following configuration shows how (binding to the
     install phase in this case):
 
@@ -185,7 +185,7 @@ Copying specific artifacts
     <<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 <localRepotorityDirectory>'s value 
+    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.