Apache
/
maven
mirror of https://github.com/apache/maven.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

more fixes on the ant task doco 

git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@320956 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Brett Leslie Porter 2005-10-14 00:49:57 +00:00
parent 46479bda43
commit 61d71e17ff
1 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
maven-site/src/site/apt/ant-tasks.apt
View File

@ -96,16 +96,23 @@ Using the Antlib
-----
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, and assuming
you passed <<<filesetId="dependeny.fileset">>> to the <<<dependencies>>> task, you could use the following:
files into a particular location. For example, to populate <<<WEB-INF/lib>>> with your dependencies
you could use the following:
-----
<dependencies filesetId="dependency.fileset" useScope="runtime">
...
</dependencies>
<copy todir="${webapp.output}/WEB-INF/lib">
<fileset refid="depdendency.fileset" />
<fileset refid="dependency.fileset" />
<mapper type="flatten" />
</copy>
-----
Note the <<<useScope>>> attribute in this call. This ensures that your web application only includes your compile
and runtime dependencies, excluding those that are only for testing or are expected to already be provided in
the servlet container.
You can also specify a <<<scope>>> parameter on each dependency. This changes the behaviour of
transitive dependencies and is useful for building different types of classpaths. To see how it affects
the behaviour of the dependencies, see the {{{dependencies.html#Dependency_Scope} Dependency Mechanism}}