maven-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From arami...@apache.org
Subject svn commit: r427484 - in /maven/plugins/trunk/maven-dependency-plugin: ./ src/site/ src/site/apt/ src/site/apt/examples/
Date Tue, 01 Aug 2006 08:08:41 GMT
Author: aramirez
Date: Tue Aug  1 01:08:39 2006
New Revision: 427484

URL: http://svn.apache.org/viewvc?rev=427484&view=rev
Log:
PR: MDEP-30

modified docs and added examples

Added:
    maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/
    maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copy-direct-dependencies.apt
    maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copying-artifacts.apt
    maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copying-unpacking-direct-dependencies.apt
    maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copying-unpacking.apt
    maven/plugins/trunk/maven-dependency-plugin/src/site/apt/index.apt
    maven/plugins/trunk/maven-dependency-plugin/src/site/apt/usage.apt
Modified:
    maven/plugins/trunk/maven-dependency-plugin/pom.xml
    maven/plugins/trunk/maven-dependency-plugin/src/site/site.xml

Modified: maven/plugins/trunk/maven-dependency-plugin/pom.xml
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/pom.xml?rev=427484&r1=427483&r2=427484&view=diff
==============================================================================
--- maven/plugins/trunk/maven-dependency-plugin/pom.xml (original)
+++ maven/plugins/trunk/maven-dependency-plugin/pom.xml Tue Aug  1 01:08:39 2006
@@ -2,7 +2,7 @@
     <parent>
        <artifactId>maven-plugins</artifactId>
        <groupId>org.apache.maven.plugins</groupId>
-       <version>1</version>
+       <version>2-SNAPSHOT</version>
      </parent>
   <modelVersion>4.0.0</modelVersion>
   <groupId>org.apache.maven.plugins</groupId>
@@ -10,6 +10,9 @@
   <packaging>maven-plugin</packaging>
   <name>Dependency Maven Plugin</name>
   <version>2.0-SNAPSHOT</version>
+  <prerequisites>
+    <maven>2.0.3</maven>
+  </prerequisites>
   <issueManagement>
     <system>JIRA</system>
     <url>http://jira.codehaus.org/browse/MDEP</url>
@@ -130,7 +133,7 @@
       <version>1.1</version>
     </dependency>
   </dependencies>
-  <reporting>
+  <!--reporting>
     <plugins>
       <plugin>
         <groupId>org.codehaus.mojo</groupId>
@@ -138,7 +141,5 @@
         <version>2.0-beta-1</version>
       </plugin>
     </plugins>
-  </reporting>
-    
-    
+  </reporting-->
 </project>

Added: maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copy-direct-dependencies.apt
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copy-direct-dependencies.apt?rev=427484&view=auto
==============================================================================
--- maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copy-direct-dependencies.apt
(added)
+++ maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copy-direct-dependencies.apt
Tue Aug  1 01:08:39 2006
@@ -0,0 +1,80 @@
+  ------
+  Copying Direct Dependencies
+  ------
+  Allan Ramirez
+  Brian Fox
+  ------
+  July 2006
+  ------
+
+Copying Direct Dependencies
+
+   Direct dependencies are the dependencies declared in your pom. To be able
+   to copy them with their transitive dependencies, use the
+   <<<dependency:copy-dependencies>>> mojo and configure the plugin like
+   the sample below:
+
++---+
+<project>
+  [...]
+  <build>
+   <plugins>
+     <plugin>
+        <groupId>org.apache.maven.plugin</groupId>
+        <artifactId>dependency-maven-plugin</artifactId>
+        <executions>
+          <execution>
+            <id>copy-dependencies</id>
+            <phase>package</phase>
+            <goals>
+              <goal>copy-dependencies</goal>
+            </goals>
+            <configuration>
+              <outputDirectory>${project.build.directory}/alternateLocation</outputDirectory>
+              <overWriteReleases>false</overWriteReleases>
+              <overWriteSnapshots>true</overWriteSnapshots>
+            </configuration>
+          </execution>
+        </executions>
+      </plugin>
+    </plugins>
+  </build>
+  [...]
+</project>
++---+
+
+* Excluding Transitive Dependencies
+
+   As mentioned, transitive dependencies are copied by default. However, it
+   can also be excluded by setting the <<<excludeTransitive>>> property
to
+   <<true>>.
+
++---+
+<project>
+  [...]
+  <build>
+   <plugins>
+     <plugin>
+        <groupId>org.apache.maven.plugin</groupId>
+        <artifactId>dependency-maven-plugin</artifactId>
+        <executions>
+          <execution>
+            <id>copy-dependencies</id>
+            <phase>package</phase>
+            <goals>
+              <goal>copy-dependencies</goal>
+            </goals>
+            <configuration>
+              <outputDirectory>${project.build.directory}/alternateLocation</outputDirectory>
+              <overWriteReleases>false</overWriteReleases>
+              <overWriteSnapshots>true</overWriteSnapshots>
+              <excludeTransitive>true</excludeTransitive>
+            </configuration>
+          </execution>
+        </executions>
+      </plugin>
+    </plugins>
+  </build>
+  [...]
+</project>
++---+
\ No newline at end of file

Added: maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copying-artifacts.apt
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copying-artifacts.apt?rev=427484&view=auto
==============================================================================
--- maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copying-artifacts.apt
(added)
+++ maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copying-artifacts.apt
Tue Aug  1 01:08:39 2006
@@ -0,0 +1,98 @@
+  ------
+  Copying Specific Artifacts
+  ------
+  Allan Ramirez
+  Brian Fox
+  ------
+  July 2006
+  ------
+
+Copying Specific Artifacts
+
+  In copying specific artifacts, you need to bind the <<<dependency:copy>>>
+  mojo to a lifecycle, configure the plugin and specify the artifacts you
+  want to copy. Just like the following:
+
++---+
+<project>
+  [...]
+  <build>
+   <plugins>
+     <plugin>
+        <groupId>org.apache.maven.plugin</groupId>
+        <artifactId>dependency-maven-plugin</artifactId>
+        <executions>
+          <execution>
+            <id>copy</id>
+            <phase>package</phase>
+            <goals>
+              <goal>copy</goal>
+            </goals>
+            <configuration>
+              <artifactItems>
+                <artifactItem>
+                  <groupId>junit</groupId>
+                  <artifactId>junit</artifactId>
+                  <version>3.8.1</version>
+                  <type>jar</type>
+                  <overWrite>false</overWrite>
+                  <outputDirectory>${project.build.directory}/alternateLocation</outputDirectory>
+                  <destFileName>optional-new-name.jar</destFileName>
+                </artifactItem>
+              </artifactItems>
+              <outputDirectory>${project.build.directory}/wars</outputDirectory>
+              <overWriteReleases>false</overWriteReleases>
+              <overWriteSnapshots>true</overWriteSnapshots>
+            </configuration>
+          </execution>
+        </executions>
+      </plugin>
+    </plugins>
+  </build>
+  [...]
+</project>
++---+
+
+    Then after executing <<<mvn package>>> the artifact (junit) is copied
to the
+    givin alternateLocation.
+
+    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
+    install phase so that the artifact exists in the repository. The following
+    configuration shows how:
+
++---+
+ <project>
+  [...]
+  <build>
+    <plugins>
+      <plugin>
+        <groupId>org.apache.maven.plugin</groupId>
+        <artifactId>dependency-maven-plugin</artifactId>
+        <executions>
+          <execution>
+            <id>copy-installed</id>
+            <phase>install</phase>
+            <goals>
+              <goal>copy</goal>
+            </goals>
+            <configuration>
+              <artifactItems>
+                <artifactItem>
+                  <groupId>${project.groupId}</groupId>
+                  <artifactId>${project.artifactId}</artifactId>
+                  <version>${project.version}</version>
+                  <type>${project.packaging}</type>
+                </artifactItem>
+              </artifactItems>
+              <outputDirectory>some-other-place</outputDirectory>
+            </configuration>
+          </execution>
+        </executions>
+      </plugin>
+    </plugins>
+  </build>
+  [...]
+</project>
++---+
+

Added: maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copying-unpacking-direct-dependencies.apt
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copying-unpacking-direct-dependencies.apt?rev=427484&view=auto
==============================================================================
--- maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copying-unpacking-direct-dependencies.apt
(added)
+++ maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copying-unpacking-direct-dependencies.apt
Tue Aug  1 01:08:39 2006
@@ -0,0 +1,47 @@
+  ------
+  Unpacking the Copied Direct Dependencies
+  ------
+  Allan Ramirez
+  Brian Fox
+  ------
+  July 2006
+  ------
+
+Unpacking the Copied Direct Dependencies
+
+  This is pretty much alike with {{{copy-direct-dependencies.html}Copying Direct Dependencies}}
+  example. The difference is that the copied direct dependencies has been unpacked,
+  including the transitive dependencies. To unpack the copied artifacts, use the
+  <<<dependency:unpack-dependencies>>> mojo and configure the dependency
plugin
+  to something like the sample below:
+
++---+
+<project>
+  [...]
+  <build>
+   <plugins>
+     <plugin>
+        <groupId>org.apache.maven.plugin</groupId>
+        <artifactId>dependency-maven-plugin</artifactId>
+        <executions>
+          <execution>
+            <id>unpack-dependencies</id>
+            <phase>package</phase>
+            <goals>
+              <goal>unpack-dependencies</goal>
+            </goals>
+            <configuration>
+              <outputDirectory>${project.build.directory}/alternateLocation</outputDirectory>
+              <overWriteReleases>false</overWriteReleases>
+              <overWriteSnapshots>true</overWriteSnapshots>
+            </configuration>
+          </execution>
+        </executions>
+      </plugin>
+    </plugins>
+  </build>
+  [...]
+</project>
++---+
+
+

Added: maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copying-unpacking.apt
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copying-unpacking.apt?rev=427484&view=auto
==============================================================================
--- maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copying-unpacking.apt
(added)
+++ maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/copying-unpacking.apt
Tue Aug  1 01:08:39 2006
@@ -0,0 +1,62 @@
+  ------
+  Unpacking the Copied Specific Artifacts
+  ------
+  Allan Ramirez
+  Brian Fox
+  ------
+  July 2006
+  ------
+
+Unpacking the Copied Specific Artifacts
+
+  This is pretty much alike with {{{copying-artifacts.html}Copying Specific Artifacts}}
+  example. The difference is that the copied artifacts has been unpacked.
+  To unpack the copied artifacts, use the <<<dependency:unpack>>> mojo
and
+  configure the plugin into something like the sample below:
+
++---+
+ <project>
+   [...]
+   <build>
+    <plugins>
+      <plugin>
+         <groupId>org.apache.maven.plugin</groupId>
+         <artifactId>dependency-maven-plugin</artifactId>
+         <executions>
+           <execution>
+             <id>unpack</id>
+             <phase>package</phase>
+             <goals>
+               <goal>unpack</goal>
+             </goals>
+             <configuration>
+               <artifactItems>
+                 <artifactItem>
+                   <groupId>junit</groupId>
+                   <artifactId>junit</artifactId>
+                   <version>3.8.1</version>
+                   <type>jar</type>
+                   <overWrite>false</overWrite>
+                   <outputDirectory>${project.build.directory}/alternateLocation</outputDirectory>
+                   <destFileName>optional-new-name.jar</destFileName>
+                 </artifactItem>
+               </artifactItems>
+               <outputDirectory>${project.build.directory}/wars</outputDirectory>
+               <overWriteReleases>false</overWriteReleases>
+               <overWriteSnapshots>true</overWriteSnapshots>
+             </configuration>
+           </execution>
+         </executions>
+       </plugin>
+     </plugins>
+   </build>
+   [...]
+ </project>
++---+
+
+  And after invoking <<<mvn package>>>, the copied artifacts are unpacked.
+
+
+
+
+

Added: maven/plugins/trunk/maven-dependency-plugin/src/site/apt/index.apt
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/src/site/apt/index.apt?rev=427484&view=auto
==============================================================================
--- maven/plugins/trunk/maven-dependency-plugin/src/site/apt/index.apt (added)
+++ maven/plugins/trunk/maven-dependency-plugin/src/site/apt/index.apt Tue Aug  1 01:08:39
2006
@@ -0,0 +1,66 @@
+  ------
+  Introduction
+  ------
+  Allan Ramirez
+  Brian Fox
+  ------
+  July 2006
+  ------
+
+Maven Dependency Plugin
+
+  The dependency plugin provides the capability to manipulate artifacts. It
+  can copy and/or unpack artifacts from local or remote repositories to a
+  specified location.
+
+* Goals Overview
+
+  Dependency plugin has 8 goals:
+
+	*{{{copy-mojo.html}dependency:copy}} takes a list of artifacts defined in
+	the plugin configuration section and copies them to a specified location,
+	renaming them or stripping the version if desired. This goal can resolve
+	the artifacts from remote repositories if they don't exist in local.
+
+	*{{{copy-dependencies-mojo.html}dependency:copy-dependencies}} takes the
+	list of direct dependencies and optionally transitive dependencies and
+	copies them to a specified location, stripping the version if desired.
+	This goal can also be run from the command line.
+
+	*{{{unpack-mojo.html}dependency:unpack}} like copy but unpacks.
+
+	*{{{unpack-dependencies-mojo.html}dependency:unpack-dependencies}} like
+	copy-dependencies but unpacks.
+
+	*{{{resolve-mojo.html}dependency:resolve}} tells Maven to resolve test
+	scope dependencies and displays the version.
+
+	*{{{resolve-mojo.html}dependency:sources}} tells Maven to resolve test
+	scope dependencies and their source attachments, and displays the version.
+
+	*{{{resolve-plugins-mojo.html}dependency:resolve-plugins}} Tells Maven to
+	resolve plugins and their dependencies.
+
+    *{{{go-offline-mojo.html}dependency:go-offline}} tells Maven to resolve
+    everything this project is dependent on (dependencies, plugins, reports)
+    in preparation for going offline.
+
+  []
+
+* Usage
+
+  Instructions on how to use the dependency plugin can be found {{{usage.html}here}}.
+
+* Examples
+
+  The following examples show how to use the dependency plugin in more advanced usecases:
+
+  * {{{examples/copying-artifacts.html}Copying Specific Artifacts}}
+
+  * {{{examples/copy-direct-dependencies.html}Copying Direct Dependencies}}
+
+  * {{{examples/copying-unpacking.html}Unpacking the Copied Specific Artifacts}}
+
+  * {{{examples/copying-unpacking-direct-dependencies.html}Unpacking the Copied Direct Dependencies}}
+
+  []

Added: maven/plugins/trunk/maven-dependency-plugin/src/site/apt/usage.apt
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/src/site/apt/usage.apt?rev=427484&view=auto
==============================================================================
--- maven/plugins/trunk/maven-dependency-plugin/src/site/apt/usage.apt (added)
+++ maven/plugins/trunk/maven-dependency-plugin/src/site/apt/usage.apt Tue Aug  1 01:08:39
2006
@@ -0,0 +1,288 @@
+  ------
+  Usage
+  ------
+  Allan Ramirez
+  Brian Fox
+  ------
+  July 2006
+  ------
+
+Usage
+
+* The <<<dependency:copy>>> mojo
+
+   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 output directory is specified but can be overriden for
+   each ArtifactItem by setting the optional outputDirectory field. An
+   optional new name can be set to rename while copying. The artifact version
+   is optional. If not set, the plugin will attempt to resolve from the
+   dependencyManagement section.
+
+   Artifacts are copied using the following rules:
+
+     * If the artifactItem.overWrite is set, use that value.
+
+     * Releases use the overWriteReleases value (default = true)
+
+     * Snapshots use the overWriteSnapshots value (default = false)
+
+     []
+
+   Configure the plugin something like this:
+
++---+
+<project>
+  [...]
+  <build>
+   <plugins>
+     <plugin>
+        <groupId>org.apache.maven.plugin</groupId>
+        <artifactId>dependency-maven-plugin</artifactId>
+        <executions>
+          <execution>
+            <id>copy</id>
+            <phase>package</phase>
+            <goals>
+              <goal>copy</goal>
+            </goals>
+            <configuration>
+              <artifactItems>
+                <artifactItem>
+                  <groupId>[ groupId ]</groupId>
+                  <artifactId>[ artifactId ]</artifactId>
+                  <version>[ version ]</version>
+                  <type>[ packaging ]</type>
+                  <overWrite>[ true or false ]</overWrite>
+                  <outputDirectory>[ output directory ]</outputDirectory>
+                  <destFileName>[ filename ]</destFileName>
+                </artifactItem>
+              </artifactItems>
+              <!-- other configurations here -->
+            </configuration>
+          </execution>
+        </executions>
+      </plugin>
+    </plugins>
+  </build>
+  [...]
+</project>
++---+
+
+* The <<<dependency:copy-dependencies>>> mojo
+
+   This goal can be bound to a lifecycle and configured in your pom.xml.
+   It will resolve the dependencies (including transitive dependencies) from
+   the repository and place a copy in the specified location. All scopes are
+   included by default, but it can be limited to a single scope.
+
+   The artifacts can be placed in subfolders based on type. For example:
+
+   \outputDirectory
+
+   \outputDirectory\jars
+
+   \outputDirectory\wars
+
+   The artifacts can be placed in a subfolder per artifact. For example:
+   \outputDirectory\junit-junit-3.8.1\
+   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
+   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
+   the sources for all dependencies and copy them.
+
+   By default, SNAPSHOTs are always overwritten, Releases are not. This can be
+   changed via the optional parameters.
+
+   The goal can also be launched from the command line like:
+   <<<mvn dependency:copy-dependencies [optional params]>>>
+
++---+
+<project>
+  [...]
+  <build>
+   <plugins>
+     <plugin>
+        <groupId>org.apache.maven.plugin</groupId>
+        <artifactId>dependency-maven-plugin</artifactId>
+        <executions>
+          <execution>
+            <id>copy-dependencies</id>
+            <phase>package</phase>
+            <goals>
+              <goal>copy-dependencies</goal>
+            </goals>
+            <configuration>
+                <!-- configure the plugin here -->
+            </configuration>
+          </execution>
+        </executions>
+      </plugin>
+    </plugins>
+  </build>
+  [...]
+</project>
++---+
+
+
+* The <<<dependency:unpack>>> mojo
+
+   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
+   ArtifactItem by setting the optional outputDirectory field. Artifacts are
+   unpacked using the following rules:
+
+     *If the artifactItem.overWrite is set, use that value.
+
+     *Releases use the overWriteReleases value (default = true)
+
+     *Snapshots use the overWriteSnapshots value (default = false)
+
+   The artifact version is optional. If not set, the plugin will attempt to
+   resolve from the dependencyManagement section.
+
++---+
+<project>
+  [...]
+  <build>
+   <plugins>
+     <plugin>
+        <groupId>org.apache.maven.plugin</groupId>
+        <artifactId>dependency-maven-plugin</artifactId>
+        <executions>
+          <execution>
+            <id>unpack</id>
+            <phase>package</phase>
+            <goals>
+              <goal>unpack</goal>
+            </goals>
+            <configuration>
+                <!-- configure the plugin here -->
+            </configuration>
+          </execution>
+        </executions>
+      </plugin>
+    </plugins>
+  </build>
+  [...]
+</project>
++---+
+
+* The <<<dependency:unpack-dependencies>>> mojo
+
+   This goal can be bound to a lifecycle and configured in your pom.xml.
+   It will resolve the dependencies (including transitive dependencies) from
+   the repository and unpack them to the specified location. All scopes are
+   included by default, but it can be limited to a single scope.
+
+   Unpack-dependencies includes transitive dependencies by default. To include
+   only direct dependencies, set the excludeTransitive parameter to true.
+
+   Dependencies can be included or excluded by a list of types. See
+   {{{unpack-dependencies-mojo.html}unpack-dependencies}} for details.
+
+   The artifacts can be unpacked in subfolders based on type. For example:
+
+   \outputDirectory
+
+   \outputDirectory\jars
+
+   \outputDirectory\wars
+
+   The artifacts can be placed in a subfolder per artifact. For example:
+   \outputDirectory\junit-junit-3.8.1\
+   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
+   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
+   the sources for all dependencies and unpack them.
+
+   By default, SNAPSHOTs are always overwritten, Releases are not. This can be
+   changed via the optional parameters.
+
+   The goal can also be launched from the command line like:
+   <<<mvn dependency:unpack-dependencies [optional params]>>>
+
++---+
+<project>
+  [...]
+  <build>
+   <plugins>
+     <plugin>
+        <groupId>org.apache.maven.plugin</groupId>
+        <artifactId>dependency-maven-plugin</artifactId>
+        <executions>
+          <execution>
+            <id>unpack-dependencies</id>
+            <phase>package</phase>
+            <goals>
+              <goal>unpack-dependencies</goal>
+            </goals>
+            <configuration>
+                <!-- configure the plugin here -->
+            </configuration>
+          </execution>
+        </executions>
+      </plugin>
+    </plugins>
+  </build>
+  [...]
+</project>
++---+
+
+* The <<<dependency:resolve>>> mojo
+
+  Resolve is intended to be used from the command line like:
+  <<<mvn dependency:resolve -Dsilent=true>>>
+
+  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
+  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.
+
+  Artifacts can also be resolved by specifying the classifer 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:resolve -Dclassifer=test-jar>>> will try to find the
+  test-jar for all dependencies resolve them to the local repository.
+
+* The <<<dependency:sources>>> mojo
+
+  Sources is intended to be used from the command line like:
+  <<<mvn dependency:sources -Dsilent=true>>>
+
+  This is the same as the resolve goal except it includes the source
+  attachments if they exist.  This is useful when you want the source
+  attachments downloaded to your local repository and
+  you don't want to use the eclipse plugin to do this since the eclipse plugin
+  creates/overwrites the eclipse files.
+
+* The <<<dependency:resolve-plugins>>> mojo
+
+  Resolve-plugins is intended to be used from the command line like:
+  <<<mvn dependency:resolve-plugins -Dsilent=true -DexcludeTransitive=true>>>
+
+  This is the same as the resolve goal except it resolves plugins and
+  optionally their dependencies.
+
+* The <<<dependency:go-offline>>> mojo
+
+  This goal is exactly the same as calling
+  <<<mvn dependency:resolve dependency:resolve-plugins>>>.
+

Modified: maven/plugins/trunk/maven-dependency-plugin/src/site/site.xml
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/src/site/site.xml?rev=427484&r1=427483&r2=427484&view=diff
==============================================================================
--- maven/plugins/trunk/maven-dependency-plugin/src/site/site.xml (original)
+++ maven/plugins/trunk/maven-dependency-plugin/src/site/site.xml Tue Aug  1 01:08:39 2006
@@ -1,24 +1,26 @@
 <?xml version="1.0" encoding="ISO-8859-1"?>
 
 <!--
- Copyright 2005-2006 Brian Fox (brianefox@gmail.com)
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
-      http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
+/*
+ * Copyright 2001-2005 The Apache Software Foundation.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *      http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
 -->
 
 <project name="Maven Dependency Plugin">
   <bannerLeft>
-    <name>Maven Idea Plugin</name>
+    <name>Maven Rar Plugin</name>
     <src>http://maven.apache.org/images/apache-maven-project.png</src>
     <href>http://maven.apache.org/</href>
   </bannerLeft>
@@ -27,13 +29,20 @@
   </bannerRight>
   <body>
     <links>
-      <item name="Maven" href="http://maven.apache.org/maven2"/>
+      <item name="Maven 2" href="http://maven.apache.org/maven2/"/>
     </links>
+
     <menu name="Overview">
-      <item name="Plugin Goals" href="index.html"/>
-      <item name="Introduction" href="introduction.html"/>
-      <item name="How to Use" href="howto.html"/>
-      <item name="Javadoc" href="apidocs/index.html"/>
+      <item name="Introduction" href="index.html"/>
+      <item name="Usage" href="usage.html"/>
+      <item name="Goals" href="plugin-info.html" />
+      <item name="FAQ" href="faq.html"/>
+    </menu>
+    <menu name="Examples">
+      <item name="Copying Specific Artifacts" href="examples/copying-artifacts.html" />
+      <item name="Copying Direct Dependencies" href="examples/copy-direct-dependencies.html"
/>
+      <item name="Unpacking the Copied Specific Artifacts" href="examples/copying-unpacking.html"
/>
+      <item name="Unpacking the Copied Direct Dependencies" href="examples/copying-unpacking-direct-dependencies.html"
/>
     </menu>
     ${reports}
   </body>



Mime
View raw message