Author: pgier
Date: Thu Oct 2 13:59:03 2008
New Revision: 701243
URL: http://svn.apache.org/viewvc?rev=701243&view=rev
Log:
[MANTTASKS-114] Small site improvement. Add an example of using the properties
that are set during dependency resolution.
Modified:
maven/ant-tasks/branches/maven-ant-tasks-2.0.x/src/site/apt/usage.apt
Modified: maven/ant-tasks/branches/maven-ant-tasks-2.0.x/src/site/apt/usage.apt
URL:
http://svn.apache.org/viewvc/maven/ant-tasks/branches/maven-ant-tasks-2.0.x/src/site/apt/usage.apt?rev=701243&r1=701242&r2=701243&view=diff
==============================================================================
--- maven/ant-tasks/branches/maven-ant-tasks-2.0.x/src/site/apt/usage.apt
(original)
+++ maven/ant-tasks/branches/maven-ant-tasks-2.0.x/src/site/apt/usage.apt Thu
Oct 2 13:59:03 2008
@@ -60,6 +60,14 @@
</javac>
-----
+ <(since 2.0.8)> For each dependency resolved using either inline declaration
or a pom reference, the property
+ <<<groupId:artifactId:type[:classifier]>>> is defined pointing to the
corresponding file. For example,
+ a resolved dependency on junit can be accessed in the following way.
+
+-----
+<echo message="JUnit jar file downloaded to ${junit:junit:jar}"/>
+-----
+
Another option you can use is <<<filesetId>>>, which will give you a fileset
reference that can be used to copy
files into a particular location. For example, to populate <<<WEB-INF/lib>>>
with your dependencies
you could use the following:
