svn commit: r1398940 - /maven/plugins/trunk/maven-dependency-plugin/src/site/apt/usage.apt.vm

[rf...@apache.org]

Author: rfscholte
Date: Tue Oct 16 19:29:08 2012
New Revision: 1398940

URL: http://svn.apache.org/viewvc?rev=1398940&view=rev
Log:
Fix typos of usage page

Modified:
    maven/plugins/trunk/maven-dependency-plugin/src/site/apt/usage.apt.vm

Modified: maven/plugins/trunk/maven-dependency-plugin/src/site/apt/usage.apt.vm
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/src/site/apt/usage.apt.vm?rev=1398940&r1=1398939&r2=1398940&view=diff
==============================================================================
--- maven/plugins/trunk/maven-dependency-plugin/src/site/apt/usage.apt.vm (original)
+++ maven/plugins/trunk/maven-dependency-plugin/src/site/apt/usage.apt.vm Tue Oct 16 19:29:08 2012
@@ -43,7 +43,7 @@ Usage
    This goal is meant to be bound to a lifecycle phase and configured in your
    <<<pom.xml>>>. It will resolve the artifact from the repository and place a copy
    in the specified location. Multiple artifacts can be defined in a single
-   execution. A default output directory is specified but can be overriden for
+   execution. A default output directory is specified but can be overridden for
    each ArtifactItem by setting the optional outputDirectory field. An
    optional new name can be set to rename or the version stripped while copying. 
    
@@ -172,11 +172,11 @@ mvn dependency:copy
    This feature also works with the subfolders per type. For example:
    \outputDirectory\jars\junit-junit-3.8.1\
 
-   Artifacts can also be resolved by specifying the classifer and optionally
+   Artifacts can also be resolved by specifying the classifier and optionally
    type. Type is only used with the classifier and defaults to java-sources.
    When the classifier is set, the list of dependencies is used as the base to
-   resolve artifacts with the classifer and type. For example:
-   <<<mvn dependency:copy-dependencies -Dclassifer=sources>>> will try to find
+   resolve artifacts with the classifier and type. For example:
+   <<<mvn dependency:copy-dependencies -Dclassifier=sources>>> will try to find
    the sources for all dependencies and copy them.
 
   Also included is the ability to include or exclude by type (war, jar etc), scope (runtime, test, etc), classifier (jdk14, sources, etc), groupId, artifactId, or a combination of them. 
@@ -223,7 +223,7 @@ mvn dependency:copy
    This goal is meant to be bound to a lifecycle and configured in your pom.xml.
    It will resolve the artifact from the repository and place a copy in the
    specified location. Multiple artifacts can be defined in a single execution.
-   A default outputDirectory is specified but can be overriden for each
+   A default outputDirectory is specified but can be overridden for each
    ArtifactItem by setting the optional outputDirectory field. 
    
    A single artifact can be unpacked multiple times if different include/exclude parameters
@@ -330,11 +330,11 @@ mvn dependency:unpack
    This feature also works with the subfolders per type. For example:
    \outputDirectory\jars\junit-junit-3.8.1\
 
-   Artifacts can also be resolved by specifying the classifer and optionally
+   Artifacts can also be resolved by specifying the classifier and optionally
    type. Type is only used with the classifier and defaults to java-sources.
    When the classifier is set, the list of dependencies is used as the base to
-   resolve artifacts with the classifer and type. For example:
-   <<<mvn dependency:unpack-dependencies -Dclassifer=sources>>> will try to find
+   resolve artifacts with the classifier and type. For example:
+   <<<mvn dependency:unpack-dependencies -Dclassifier=sources>>> will try to find
    the sources for all dependencies and unpack them.
    
    Filters can be applied to include or exclude certain file or filesets as necessary
@@ -415,7 +415,7 @@ mvn dependency:unpack
   This goal simply tells maven to resolve all test scope (includes compile)
   dependencies and then displays the resolved versions. This is intended to
   help ensure all dependencies are downloaded to the local repository. This is
-  usefull when troubleshooting or during intermittent remote repository
+  useful when troubleshooting or during intermittent remote repository
   failures when repeatedly building multiproject modules is undersirable and
   the build is failing on dependency resolution. It can also be used to quickly
   determine how versions are being resolved.