You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@click.apache.org by sa...@apache.org on 2009/11/03 11:32:44 UTC

svn commit: r832380 - /incubator/click/trunk/click/documentation/xdocs/src/docbook/click/chapter-configuration.xml

Author: sabob
Date: Tue Nov  3 10:32:40 2009
New Revision: 832380

URL: http://svn.apache.org/viewvc?rev=832380&view=rev
Log:
document DeployTask nested FileSets

Modified:
    incubator/click/trunk/click/documentation/xdocs/src/docbook/click/chapter-configuration.xml

Modified: incubator/click/trunk/click/documentation/xdocs/src/docbook/click/chapter-configuration.xml
URL: http://svn.apache.org/viewvc/incubator/click/trunk/click/documentation/xdocs/src/docbook/click/chapter-configuration.xml?rev=832380&r1=832379&r2=832380&view=diff
==============================================================================
--- incubator/click/trunk/click/documentation/xdocs/src/docbook/click/chapter-configuration.xml (original)
+++ incubator/click/trunk/click/documentation/xdocs/src/docbook/click/chapter-configuration.xml Tue Nov  3 10:32:40 2009
@@ -1083,7 +1083,7 @@
           that can be found in your Click distribution under the <emphasis>lib</emphasis>
           folder.
           </para>
-          <para>Here is an example:
+          <para>Here is a basic example:
           </para>
           <programlisting language="xml"><![CDATA[<target name="deploy" description="Deploy static resources">
     <taskdef name="deploy"
@@ -1125,10 +1125,31 @@
           will be served from.
           </para>
 
+          <para>The DeployTask also supports nested
+          <ulink url="http://ant.apache.org/manual/CoreTypes/fileset.html">FileSets</ulink>
+          if you need to deploy resources from multiple source locations. For
+          example:</para>
+          <programlisting language="xml"><![CDATA[<target name="deploy" description="Deploy static resources">
+    <taskdef name="deploy"
+             classname="org.apache.click.tools.deploy.DeployTask"
+             classpath="<click-distribution>/lib/click-dev-tasks-1.1.jar"/>
+
+    <deploy todir="${dir.webapp}">
+        <fileset dir="<webapp-root>/WEB-INF">
+            <include name="**/classes"/>
+            <include name="**/*.jar"/>
+        </fileset>
+        <fileset dir="/some/folder/with/jars">
+            <include name="lib-with-resources.jar"/>
+            <include name="another-lib-with-resources.jar"/>
+        </fileset>
+    </deploy>
+</target>]]> </programlisting>
+
           <para>The DeployTask also generates an HTML report in the same folder
           where the build script is executed from. The report will indicate
           which resources was deployed successfully and which resources
-          in your webapp root directory is outdated. (An outdated resource mean
+          in your webapp root directory is outdated. (An outdated resource means
           that the resource in the <emphasis>click-xxx.jar</emphasis> differs
           from the resource currently present in your webapp root directory.
           This can happen when upgrading to a new version of Click)