Submitted by: Larry Shatzer git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@277023 13f79535-47bb-0310-9956-ffa450edef68master
@@ -62,7 +62,7 @@ | |||||
<pre> | <pre> | ||||
<blgenclient ejbjar="lib/secutest-ejb.jar" clientjar="lib/client.jar" debug="true" mode="fork"> version="5"> | <blgenclient ejbjar="lib/secutest-ejb.jar" clientjar="lib/client.jar" debug="true" mode="fork"> version="5"> | ||||
<classpath> | <classpath> | ||||
<pathelement locacation="mymodule.jar"/> | |||||
<pathelement location="mymodule.jar"/> | |||||
</classpath> | </classpath> | ||||
</blgenclient> | </blgenclient> | ||||
</pre> | </pre> | ||||
@@ -91,7 +91,7 @@ | |||||
<tr> | <tr> | ||||
<td valign="top">diagnostic</td> | <td valign="top">diagnostic</td> | ||||
<td valign="top"> | <td valign="top"> | ||||
Generates a text file with debugging infomation based on the target grammar. | |||||
Generates a text file with debugging information based on the target grammar. | |||||
</td> | </td> | ||||
<td valign="top" align="center">No</td> | <td valign="top" align="center">No</td> | ||||
</tr> | </tr> | ||||
@@ -17,7 +17,7 @@ | |||||
</ul> | </ul> | ||||
<p>These ant tasks are wrappers around Continuus Source Manager. They have been tested | <p>These ant tasks are wrappers around Continuus Source Manager. They have been tested | ||||
agains versions 5.1/6.2 on Windows 2000, but should work on other platforms with ccm installed.</p> | |||||
against versions 5.1/6.2 on Windows 2000, but should work on other platforms with ccm installed.</p> | |||||
<p>author: <a href="mailto:benoit.moussaud@criltelecom.com">Benoit Mousaud (benoit.moussaud@criltelecom.com) </a></p> | <p>author: <a href="mailto:benoit.moussaud@criltelecom.com">Benoit Mousaud (benoit.moussaud@criltelecom.com) </a></p> | ||||
<hr> | <hr> | ||||
<h2><a name="ccmcheckin">CCMCheckin</a></h2> | <h2><a name="ccmcheckin">CCMCheckin</a></h2> | ||||
@@ -78,7 +78,7 @@ Task to perform a Checkout command to Continuus | |||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
<td>fileset</td> | <td>fileset</td> | ||||
<td>filset containing the file to be checked out</td> | |||||
<td>fileset containing the file to be checked out</td> | |||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
<td>comment</td> | <td>comment</td> | ||||
@@ -121,7 +121,7 @@ group.</p> | |||||
</blockquote> | </blockquote> | ||||
<p>makes all <code>.test.jsp</code>, and <code>.new</code> files belong to | <p>makes all <code>.test.jsp</code>, and <code>.new</code> files belong to | ||||
group webdev. Directories begining with <code>test_</code> also will belong | |||||
group webdev. Directories beginning with <code>test_</code> also will belong | |||||
to webdev, but if there is a directory that ends in <code>.new</code> or a file | to webdev, but if there is a directory that ends in <code>.new</code> or a file | ||||
that begins with <code>test_</code> it will be unaffected.</p> | that begins with <code>test_</code> it will be unaffected.</p> | ||||
@@ -13,7 +13,7 @@ | |||||
<p>Changes the owner of a file or all files inside specified | <p>Changes the owner of a file or all files inside specified | ||||
directories. Right now it has effect only under Unix. The owner | directories. Right now it has effect only under Unix. The owner | ||||
atribute is equivalent to the coresponding argument for the chown | |||||
attribute is equivalent to the corresponding argument for the chown | |||||
command.</p> | command.</p> | ||||
<p><a href="../CoreTypes/fileset.html">FileSet</a>s, | <p><a href="../CoreTypes/fileset.html">FileSet</a>s, | ||||
@@ -121,8 +121,8 @@ owner.</p> | |||||
</blockquote> | </blockquote> | ||||
<p>makes cgi scripts, files with a <code>.old</code> extension or | <p>makes cgi scripts, files with a <code>.old</code> extension or | ||||
directories begining with <code>private_</code> belong to the user named | |||||
webadmin. A directory ending in <code>.old</code> or a file begining with | |||||
directories beginning with <code>private_</code> belong to the user named | |||||
webadmin. A directory ending in <code>.old</code> or a file beginning with | |||||
<code>private_</code> would remain unaffected.</p> | <code>private_</code> would remain unaffected.</p> | ||||
<hr> | <hr> | ||||
@@ -39,7 +39,7 @@ Sean Egan (sean at cm-logic dot com)</p> | |||||
<hr> | <hr> | ||||
<h2><a name="introduction">Introduction</a></h2> | <h2><a name="introduction">Introduction</a></h2> | ||||
<p>Ant provides several optional tasks for working with ClearCase. These tasks correspond to various | <p>Ant provides several optional tasks for working with ClearCase. These tasks correspond to various | ||||
ClearCase commands using the Cleartool program. The current tasks avaliable for Ant correspond to only | |||||
ClearCase commands using the Cleartool program. The current tasks available for Ant correspond to only | |||||
a few of the significant ClearCase commands.</p> | a few of the significant ClearCase commands.</p> | ||||
<p>More tasks can be easily added by deriving from the ClearCase class and then adding | <p>More tasks can be easily added by deriving from the ClearCase class and then adding | ||||
@@ -46,7 +46,7 @@ | |||||
</td></tr> | </td></tr> | ||||
<tr><td><blockquote> | <tr><td><blockquote> | ||||
Compiles C# source into executables or modules. csc.exe on Windows or mcs on any other platform must be on the execute path, unless another executable or the full path to that executable is specified in the <tt>executable</tt> parameter <p> All parameters are optional: <csc/> should suffice to produce a debug build of all *.cs files. However, naming an <tt>destFile</tt>stops the csc compiler from choosing an output name from random, and allows the dependency checker to determine if the file is out of date. <p> The task is a directory based task, so attributes like <b>includes="*.cs" </b> and <b>excludes="broken.cs"</b> can be used to control the files pulled in. By default, all *.cs files from the project folder down are included in the command. When this happens the output file -if not specified- is taken as the first file in the list, which may be somewhat hard to control. Specifying the output file with <tt>destFile</tt> seems prudent. <p> <p> For more complex source trees, nested <tt>src</tt> elemements can be supplied. When such an element is present, the implicit fileset is ignored. This makes sense, when you think about it :) <p> References to external files can be made through the references attribute, or (since Ant1.6), via nested <reference> filesets. With the latter, the timestamps of the references are also used in the dependency checking algorithm. <p> Example <pre><csc optimize="true" debug="false" docFile="documentation.xml" warnLevel="4" unsafe="false" targetType="exe" incremental="false" mainClass = "MainApp" destFile="NetApp.exe" > <src dir="src" includes="*.cs" /> <reference file="${testCSC.dll}" /> <define name="RELEASE" /> <define name="DEBUG" if="debug.property"/> <define name="def3" unless="def3.property"/> </csc> </pre> | |||||
Compiles C# source into executables or modules. csc.exe on Windows or mcs on any other platform must be on the execute path, unless another executable or the full path to that executable is specified in the <tt>executable</tt> parameter <p> All parameters are optional: <csc/> should suffice to produce a debug build of all *.cs files. However, naming an <tt>destFile</tt>stops the csc compiler from choosing an output name from random, and allows the dependency checker to determine if the file is out of date. <p> The task is a directory based task, so attributes like <b>includes="*.cs" </b> and <b>excludes="broken.cs"</b> can be used to control the files pulled in. By default, all *.cs files from the project folder down are included in the command. When this happens the output file -if not specified- is taken as the first file in the list, which may be somewhat hard to control. Specifying the output file with <tt>destFile</tt> seems prudent. <p> <p> For more complex source trees, nested <tt>src</tt> elements can be supplied. When such an element is present, the implicit fileset is ignored. This makes sense, when you think about it :) <p> References to external files can be made through the references attribute, or (since Ant1.6), via nested <reference> filesets. With the latter, the timestamps of the references are also used in the dependency checking algorithm. <p> Example <pre><csc optimize="true" debug="false" docFile="documentation.xml" warnLevel="4" unsafe="false" targetType="exe" incremental="false" mainClass = "MainApp" destFile="NetApp.exe" > <src dir="src" includes="*.cs" /> <reference file="${testCSC.dll}" /> <define name="RELEASE" /> <define name="DEBUG" if="debug.property"/> <define name="def3" unless="def3.property"/> </csc> </pre> | |||||
</blockquote></td></tr> | </blockquote></td></tr> | ||||
</table> | </table> | ||||
@@ -143,7 +143,7 @@ classes. Defaults to false</td> | |||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
<td valign="top">classpath</td> | <td valign="top">classpath</td> | ||||
<td valign="top">The classpath containg jars and classes for which <code><depend></code> should also | |||||
<td valign="top">The classpath containing jars and classes for which <code><depend></code> should also | |||||
check dependencies</td> | check dependencies</td> | ||||
<td valign="top" align="center">No</td> | <td valign="top" align="center">No</td> | ||||
</tr> | </tr> | ||||
@@ -427,7 +427,7 @@ and hence ant, will not complete until the weblogic instance is stopped.</p> | |||||
<h3>Nested Elements</h3> | <h3>Nested Elements</h3> | ||||
<p>The wlrun task supports nested <classpath> and <wlclasspath> | <p>The wlrun task supports nested <classpath> and <wlclasspath> | ||||
elements to set the repsective classpaths.</p> | |||||
elements to set the respective classpaths.</p> | |||||
<h3>Examples</h3> | <h3>Examples</h3> | ||||
@@ -1296,7 +1296,7 @@ the classpath of the ejbdeploy tool and set the <i>websphere.home</i> property ( | |||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
<td valign="top">ejbdeploy</td> | <td valign="top">ejbdeploy</td> | ||||
<td valign="top">Decides wether ejbdeploy is called. When you set this to true, | |||||
<td valign="top">Decides whether ejbdeploy is called. When you set this to true, | |||||
be sure, to run ant with the ibm jdk.</td> | be sure, to run ant with the ibm jdk.</td> | ||||
<td valign="top" align="center">No, defaults to true</td> | <td valign="top" align="center">No, defaults to true</td> | ||||
</tr> | </tr> | ||||
@@ -32,7 +32,7 @@ a firewall via socks. | |||||
<p> | <p> | ||||
<b>Warning: </b> there have been problems reported concerning the ftp get with newer attribute. | <b>Warning: </b> there have been problems reported concerning the ftp get with newer attribute. | ||||
Problems might be due to format of ls -l differing from what is expected by commons-net, | Problems might be due to format of ls -l differing from what is expected by commons-net, | ||||
for instance due to specificities of langage used by the ftp server in the directory listing. | |||||
for instance due to specificities of language used by the ftp server in the directory listing. | |||||
If you encounter such a problem, please send an email including a sample directory listing | If you encounter such a problem, please send an email including a sample directory listing | ||||
coming from your ftp server (ls -l on the ftp prompt). | coming from your ftp server (ls -l on the ftp prompt). | ||||
<h3>Parameters</h3> | <h3>Parameters</h3> | ||||
@@ -426,7 +426,7 @@ When removing the <code>/somedir/dirb</code> tree, | |||||
it will start at the leaves moving up to the root, so that when | it will start at the leaves moving up to the root, so that when | ||||
it tries to remove a directory it is sure all the directories under it are | it tries to remove a directory it is sure all the directories under it are | ||||
already removed. | already removed. | ||||
Obviuosly all the files in the tree must have been already deleted. | |||||
Obviously all the files in the tree must have been already deleted. | |||||
</p> | </p> | ||||
<p>As an example suppose you want to delete everything contained into | <p>As an example suppose you want to delete everything contained into | ||||
<code>/somedir</code>, so invoke first the <code><ftp></code> task with | <code>/somedir</code>, so invoke first the <code><ftp></code> task with | ||||
@@ -110,7 +110,7 @@ Instruments Java classes with <a href="http://www.reliable-systems.com/tools/">i | |||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
<td valign="top">classdir</td> | <td valign="top">classdir</td> | ||||
<td valign="top">Indicates where compiled (unistrumented) classes are located. | |||||
<td valign="top">Indicates where compiled (uninstrumented) classes are located. | |||||
This is required in order to properly update the icontrol.properties file, not | This is required in order to properly update the icontrol.properties file, not | ||||
for instrumentation.</td> | for instrumentation.</td> | ||||
<td valign="top" align="center">Only if <code>updateicontrol=true</code></td> | <td valign="top" align="center">Only if <code>updateicontrol=true</code></td> | ||||
@@ -96,7 +96,7 @@ | |||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
<td valign="top"> followSymlinks </td> | <td valign="top"> followSymlinks </td> | ||||
<td valign="top"> Boolean value. Sets whether or not symbolic links hsould be followed. </td> | |||||
<td valign="top"> Boolean value. Sets whether or not symbolic links should be followed. </td> | |||||
<td align="center"> no (defaults to <i>true</i>) </td> | <td align="center"> no (defaults to <i>true</i>) </td> | ||||
</tr> | </tr> | ||||
</table> | </table> | ||||
@@ -154,7 +154,7 @@ ImageOperation can handle nested Rotate, Draw, Rectangle, Text and Scale objects | |||||
<td align="center"> no (defaults to <i>100%</i>) </td> | <td align="center"> no (defaults to <i>100%</i>) </td> | ||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
<td valign="top"> heigth </td> | |||||
<td valign="top"> height </td> | |||||
<td valign="top"> Sets the height of the image, either as an integer or a %. </td> | <td valign="top"> Sets the height of the image, either as an integer or a %. </td> | ||||
<!-- todo: if integer, what kind? cm, px, inches, ... --> | <!-- todo: if integer, what kind? cm, px, inches, ... --> | ||||
<td align="center"> no (defaults to <i>100%</i>) </td> | <td align="center"> no (defaults to <i>100%</i>) </td> | ||||
@@ -66,7 +66,7 @@ sets of files to check for extension.</p> | |||||
</jarlib-available> | </jarlib-available> | ||||
</pre> | </pre> | ||||
<p><b>Search for extension in single file refencing external Extension</b></p> | |||||
<p><b>Search for extension in single file referencing external Extension</b></p> | |||||
<pre> | <pre> | ||||
<extension id="myext" | <extension id="myext" | ||||
extensionName="org.apache.tools.ant" | extensionName="org.apache.tools.ant" | ||||
@@ -50,7 +50,7 @@ http://java.sun.com/j2se/1.3/docs/guide/extensions/versioning.html</a>.</p> | |||||
<h4>options</h4> | <h4>options</h4> | ||||
<p><a href="../OptionalTypes/extensionset.html">ExtensionSet</a>s containing | <p><a href="../OptionalTypes/extensionset.html">ExtensionSet</a>s containing | ||||
all optional dependencies for jar. (Optional dependencies will be used if | all optional dependencies for jar. (Optional dependencies will be used if | ||||
present else they wilkl be ignored)</p> | |||||
present else they will be ignored)</p> | |||||
<h3>Examples</h3> | <h3>Examples</h3> | ||||
<p><b>Basic Manifest generated for single Extension</b></p> | <p><b>Basic Manifest generated for single Extension</b></p> | ||||
@@ -12,7 +12,7 @@ | |||||
<p>Try to locate a jar to satisfy an extension and place | <p>Try to locate a jar to satisfy an extension and place | ||||
location of jar into property. The task allows you to | location of jar into property. The task allows you to | ||||
add a number of resolvers that are capable of locating a | add a number of resolvers that are capable of locating a | ||||
library for a specifc extension. Each resolver will be attempted | |||||
library for a specific extension. Each resolver will be attempted | |||||
in specified order until library is found or no resolvers are left. | in specified order until library is found or no resolvers are left. | ||||
If no resolvers are left and failOnError is true then a BuildException | If no resolvers are left and failOnError is true then a BuildException | ||||
will be thrown.</p> | will be thrown.</p> | ||||
@@ -46,7 +46,7 @@ http://java.sun.com/j2se/1.3/docs/guide/extensions/versioning.html</a>.</p> | |||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
<td valign="top">checkExtension</td> | <td valign="top">checkExtension</td> | ||||
<td valign="top">True if librarys returned by nested resolvers should be checked to see if | |||||
<td valign="top">True if libraries returned by nested resolvers should be checked to see if | |||||
they supply extension.</td> | they supply extension.</td> | ||||
<td valign="top" align="center">No, defaults to true.</td> | <td valign="top" align="center">No, defaults to true.</td> | ||||
</tr> | </tr> | ||||
@@ -171,7 +171,7 @@ http://java.sun.com/j2se/1.3/docs/guide/extensions/versioning.html</a>.</p> | |||||
</pre> | </pre> | ||||
<p><b>Resolve Extension via multiple methods.</b> First check local file to see if it implements | <p><b>Resolve Extension via multiple methods.</b> First check local file to see if it implements | ||||
extension. If it does not then try to build it from source in parralel directory. If that | |||||
extension. If it does not then try to build it from source in parallel directory. If that | |||||
fails then finally try to download it from a website. If all steps fail then throw a build | fails then finally try to download it from a website. If all steps fail then throw a build | ||||
exception.</p> | exception.</p> | ||||
<pre> | <pre> | ||||
@@ -517,7 +517,7 @@ is set to true when invoking JJTree. | |||||
</tr> | </tr> | ||||
</table> | </table> | ||||
<p>*) <u>Footnote</u>: When running JJTree with the Ant taskdesk <i>jjtree</i> the option <code>-OUTPUT_DIRECTORY</code> must always | |||||
<p>*) <u>Footnote</u>: When running JJTree with the Ant taskdef <i>jjtree</i> the option <code>-OUTPUT_DIRECTORY</code> must always | |||||
be set, because the project's basedir and the ant working directory might differ. So even if you don't specify the jjtree taskdef | be set, because the project's basedir and the ant working directory might differ. So even if you don't specify the jjtree taskdef | ||||
<i>outputdirectory</i> JJTree will be called with the <code>-OUTPUT_DIRECTORY</code> set to the project's basedirectory. | <i>outputdirectory</i> JJTree will be called with the <code>-OUTPUT_DIRECTORY</code> set to the project's basedirectory. | ||||
But when the <code>-OUTPUT_DIRECTORY</code> is set, the <code>-OUTPUT_FILE</code> setting is handled as if relative to this | But when the <code>-OUTPUT_DIRECTORY</code> is set, the <code>-OUTPUT_FILE</code> setting is handled as if relative to this | ||||
@@ -54,7 +54,7 @@ Perform code covering functions by comparing source code line execution to the p | |||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
<td valign="top">home</td> | <td valign="top">home</td> | ||||
<td valign="top">The directory where JProbe is intalled.</td> | |||||
<td valign="top">The directory where JProbe is installed.</td> | |||||
<td align="center" valign="top">Yes</td> | <td align="center" valign="top">Yes</td> | ||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
@@ -380,7 +380,7 @@ Oro</a> in Ant classpath, to run the <tt>reference</tt> feature.</p> | |||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
<td valign="top">home</td> | <td valign="top">home</td> | ||||
<td valign="top">The directory where JProbe is intalled.</td> | |||||
<td valign="top">The directory where JProbe is installed.</td> | |||||
<td align="center" valign="top">Yes</td> | <td align="center" valign="top">Yes</td> | ||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
@@ -237,7 +237,7 @@ When used, the task hands off all dependency checking to the compiler. | |||||
</jspc> | </jspc> | ||||
</pre> | </pre> | ||||
Build all jsp pages under src/war into the destination /gensrc, in a | Build all jsp pages under src/war into the destination /gensrc, in a | ||||
package heirarchy beginning with com.i3sp.jsp. | |||||
package hierarchy beginning with com.i3sp.jsp. | |||||
<pre> | <pre> | ||||
<jspc | <jspc | ||||
@@ -284,13 +284,13 @@ or from the command line as<br> | |||||
<tr> | <tr> | ||||
<td valign="top">suppressExceptionNotSignalled</td> | <td valign="top">suppressExceptionNotSignalled</td> | ||||
<td valign="top">Tells whether we should filter out the | <td valign="top">Tells whether we should filter out the | ||||
&Exception is declared, but not signalled within the method& | |||||
&Exception is declared, but not signaled within the method& | |||||
messages in strictsignal mode.</td> | messages in strictsignal mode.</td> | ||||
<td valign="top" align="center">no</td> | <td valign="top" align="center">no</td> | ||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
<td valign="top">suppressDeprecation</td> | <td valign="top">suppressDeprecation</td> | ||||
<td valign="top">Tells wether we should filter out any deprecation-messages | |||||
<td valign="top">Tells whether we should filter out any deprecation-messages | |||||
of the compiler out.</td> | of the compiler out.</td> | ||||
<td valign="top" align="center">no</td> | <td valign="top" align="center">no</td> | ||||
</tr> | </tr> | ||||
@@ -224,7 +224,7 @@ available from the <a href="http://www.perforce.com/" target="_top">Perforce web | |||||
<td valign="top">force</td> | <td valign="top">force</td> | ||||
<td valign="top">force a refresh of files, if this attribute has | <td valign="top">force a refresh of files, if this attribute has | ||||
been set.</td> | been set.</td> | ||||
<td valign="top" align="center">no - if ommitted, it will be off, | |||||
<td valign="top" align="center">no - if omitted, it will be off, | |||||
otherwise a refresh will be forced.</td> | otherwise a refresh will be forced.</td> | ||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
@@ -43,7 +43,7 @@ The pvcs task allows the user of ant to extract the latest edition | |||||
of the source code from a PVCS repository. PVCS is a version control system | of the source code from a PVCS repository. PVCS is a version control system | ||||
developed by <a href="http://www.merant.com/products/pvcs">Merant</a>. | developed by <a href="http://www.merant.com/products/pvcs">Merant</a>. | ||||
<br> | <br> | ||||
This version has been tested agains PVCS version 6.5 and 6.6 under Windows and Solaris. | |||||
This version has been tested against PVCS version 6.5 and 6.6 under Windows and Solaris. | |||||
<hr> | <hr> | ||||
<h2><a NAME="pvcs">Pvcs Task</a></h2> | <h2><a NAME="pvcs">Pvcs Task</a></h2> | ||||
@@ -49,7 +49,7 @@ See details in the documentation of the <a href="../CoreTypes/regexp.html#implem | |||||
<td valign="top">flags</td> | <td valign="top">flags</td> | ||||
<td valign="top">The flags to use when matching the regular expression. For more | <td valign="top">The flags to use when matching the regular expression. For more | ||||
information, consult the Perl5 syntax<br /> | information, consult the Perl5 syntax<br /> | ||||
g : Global replacement. Replace all occurences found<br /> | |||||
g : Global replacement. Replace all occurrences found<br /> | |||||
i : Case Insensitive. Do not consider case in the match<br /> | i : Case Insensitive. Do not consider case in the match<br /> | ||||
m : Multiline. Treat the string as multiple lines of input, using "^" and "$" as the start or end of any line, respectively, rather than start or end of string.<br /> | m : Multiline. Treat the string as multiple lines of input, using "^" and "$" as the start or end of any line, respectively, rather than start or end of string.<br /> | ||||
s : Singleline. Treat the string as a single line of input, using "." to match any character, including a newline, which normally, it would not match.<br /> | s : Singleline. Treat the string as a single line of input, using "." to match any character, including a newline, which normally, it would not match.<br /> | ||||
@@ -60,7 +60,7 @@ See details in the documentation of the <a href="../CoreTypes/regexp.html#implem | |||||
<td valign="top">byline</td> | <td valign="top">byline</td> | ||||
<td valign="top">Process the file(s) one line at a time, executing the replacement | <td valign="top">Process the file(s) one line at a time, executing the replacement | ||||
on one line at a time (<i>true/false</i>). This is useful if you | on one line at a time (<i>true/false</i>). This is useful if you | ||||
want to only replace the first occurence of a regular expression on | |||||
want to only replace the first occurrence of a regular expression on | |||||
each line, which is not easy to do when processing the file as a whole. | each line, which is not easy to do when processing the file as a whole. | ||||
Defaults to <i>false</i>.</td> | Defaults to <i>false</i>.</td> | ||||
<td valign="top" align="center">No</td> | <td valign="top" align="center">No</td> | ||||
@@ -1,3 +1,4 @@ | |||||
<html> | <html> | ||||
<head> | <head> | ||||
@@ -33,7 +33,7 @@ jsch-0.1.14.</p> | |||||
<td valign="top">file</td> | <td valign="top">file</td> | ||||
<td valign="top">The file to copy. This can be a local path or a | <td valign="top">The file to copy. This can be a local path or a | ||||
remote path of the form <i>user[:password]@host:/directory/path</i>. | remote path of the form <i>user[:password]@host:/directory/path</i>. | ||||
<i>:password</i> can be ommitted if you use key based | |||||
<i>:password</i> can be omitted if you use key based | |||||
authentication or specify the password attribute. The way remote | authentication or specify the password attribute. The way remote | ||||
path is recognized is whether it contains @ character or not. This | path is recognized is whether it contains @ character or not. This | ||||
will not work if your localPath contains @ character.</td> | will not work if your localPath contains @ character.</td> | ||||
@@ -59,7 +59,7 @@ jsch-0.1.14.</p> | |||||
<td valign="top">todir</td> | <td valign="top">todir</td> | ||||
<td valign="top">The directory to copy to. This can be a local path | <td valign="top">The directory to copy to. This can be a local path | ||||
or a remote path of the form <i>user[:password]@host:/directory/path</i>. | or a remote path of the form <i>user[:password]@host:/directory/path</i>. | ||||
<i>:password</i> can be ommitted if you use key based | |||||
<i>:password</i> can be omitted if you use key based | |||||
authentication or specify the password attribute. The way remote | authentication or specify the password attribute. The way remote | ||||
path is recognized is whether it contains @ character or not. This | path is recognized is whether it contains @ character or not. This | ||||
will not work if your localPath contains @ character.</td> | will not work if your localPath contains @ character.</td> | ||||
@@ -209,7 +209,7 @@ authentication.</b></p> | |||||
<p><strong>Security Note:</strong> Hard coding passwords and/or usernames | <p><strong>Security Note:</strong> Hard coding passwords and/or usernames | ||||
in scp task can be a serious security hole. Consider using variable | in scp task can be a serious security hole. Consider using variable | ||||
substituion and include the password on the command line. For example:<br> | |||||
substitution and include the password on the command line. For example:<br> | |||||
<pre> | <pre> | ||||
<scp todir="${username}:${password}@host:/dir" ...> | <scp todir="${username}:${password}@host:/dir" ...> | ||||
</pre> | </pre> | ||||
@@ -85,7 +85,7 @@ print "message is %s" % message | |||||
start on the first column. | start on the first column. | ||||
</p> | </p> | ||||
<p> | <p> | ||||
The following script shows a little more complicted jruby example: | |||||
The following script shows a little more complicated jruby example: | |||||
</p> | </p> | ||||
<blockquote><pre> | <blockquote><pre> | ||||
<script language="ruby"> | <script language="ruby"> | ||||
@@ -256,7 +256,7 @@ For getting the size of a file we instantiate a <code>java.io.File</code>. So we | |||||
normal Java API here.<br> | normal Java API here.<br> | ||||
Finally we use the <echo> task for producing the output. The task is not executed by | Finally we use the <echo> task for producing the output. The task is not executed by | ||||
its execute() method, because the perform() method (implemented in Task itself) does the | its execute() method, because the perform() method (implemented in Task itself) does the | ||||
apropriate logging before and after invoking execute(). | |||||
appropriate logging before and after invoking execute(). | |||||
</p> | </p> | ||||
@@ -14,7 +14,7 @@ scripting languages supported by | |||||
<a href="http://jakarta.apache.org/bsf" target="_top">Apache BSF</a> may be | <a href="http://jakarta.apache.org/bsf" target="_top">Apache BSF</a> may be | ||||
used to define the script. Scriptdef provides a mechanism to encapsulate | used to define the script. Scriptdef provides a mechanism to encapsulate | ||||
control logic from a build within an Ant task minimizing the need for | control logic from a build within an Ant task minimizing the need for | ||||
proviuding control style tasks in Ant itself. Complex logic can be made | |||||
providing control style tasks in Ant itself. Complex logic can be made | |||||
available while retaining the simple structure of an Ant build file. Scriptdef | available while retaining the simple structure of an Ant build file. Scriptdef | ||||
is also useful for prototyping new custom tasks. Certainly as the complexity | is also useful for prototyping new custom tasks. Certainly as the complexity | ||||
of the script increases it would be better to migrate the task definition | of the script increases it would be better to migrate the task definition | ||||
@@ -123,7 +123,7 @@ more information on writing scripts, please refer to the | |||||
<h3>Examples</h3> | <h3>Examples</h3> | ||||
<p> | <p> | ||||
The following definition creates a task which supprts an attribute called | |||||
The following definition creates a task which supports an attribute called | |||||
attr and two nested elements, one being a fileset and the other a path. When | attr and two nested elements, one being a fileset and the other a path. When | ||||
executed, the resulting task logs the value of the attribute and the basedir | executed, the resulting task logs the value of the attribute and the basedir | ||||
of the first fileset. | of the first fileset. | ||||
@@ -70,7 +70,7 @@ attributes are required, depending on the tool. | |||||
<td valign="top">A fully qualified path/filename of the component to be deployed. | <td valign="top">A fully qualified path/filename of the component to be deployed. | ||||
This may be an .ear, .jar, .war, or any other type that is supported by the server. | This may be an .ear, .jar, .war, or any other type that is supported by the server. | ||||
</td> | </td> | ||||
<td>Tool dependant</td> | |||||
<td>Tool dependent</td> | |||||
</tr> | </tr> | ||||
</table> | </table> | ||||
@@ -91,22 +91,22 @@ attributes are required, depending on the tool. | |||||
<td valign="top">classpath</td> | <td valign="top">classpath</td> | ||||
<td valign="top">The classpath to be passed to the JVM running the tool. | <td valign="top">The classpath to be passed to the JVM running the tool. | ||||
The classpath may also be supplied as a nested element.</td> | The classpath may also be supplied as a nested element.</td> | ||||
<td>Tool dependant</td> | |||||
<td>Tool dependent</td> | |||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
<td valign="top">server</td> | <td valign="top">server</td> | ||||
<td valign="top">The address or URL for the server where the component will be deployed.</td> | <td valign="top">The address or URL for the server where the component will be deployed.</td> | ||||
<td>Tool dependant</td> | |||||
<td>Tool dependent</td> | |||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
<td valign="top">username</td> | <td valign="top">username</td> | ||||
<td valign="top">The user with privileges to deploy applications to the server.</td> | <td valign="top">The user with privileges to deploy applications to the server.</td> | ||||
<td>Tool dependant</td> | |||||
<td>Tool dependent</td> | |||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
<td valign="top">password</td> | <td valign="top">password</td> | ||||
<td valign="top">The password of the user with privileges to deploy applications to the server.</td> | <td valign="top">The password of the user with privileges to deploy applications to the server.</td> | ||||
<td>Tool dependant</td> | |||||
<td>Tool dependent</td> | |||||
</tr> | </tr> | ||||
</table> | </table> | ||||
@@ -231,7 +231,7 @@ WebLogic server:</p> | |||||
</pre> | </pre> | ||||
<a name="serverdeploy_jonas"> | <a name="serverdeploy_jonas"> | ||||
<h3>JOnAS (Java Open Applicaton Server) element</h3> | |||||
<h3>JOnAS (Java Open Application Server) element</h3> | |||||
<p> | <p> | ||||
The JOnAS element contains additional attributes to run the | The JOnAS element contains additional attributes to run the | ||||
<code>JonasAdmin</code> deployment tool. | <code>JonasAdmin</code> deployment tool. | ||||
@@ -31,7 +31,7 @@ jsch-0.1.9 and won't work with versions of jsch earlier than | |||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
<td valign="top">host</td> | <td valign="top">host</td> | ||||
<td valign="top">The hostname or IP adress of the remote host to which you wish to connect.</td> | |||||
<td valign="top">The hostname or IP address of the remote host to which you wish to connect.</td> | |||||
<td valign="top" align="center">Yes</td> | <td valign="top" align="center">Yes</td> | ||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
@@ -142,7 +142,7 @@ jsch-0.1.9 and won't work with versions of jsch earlier than | |||||
<p><strong>Security Note:</strong> Hard coding passwords and/or usernames | <p><strong>Security Note:</strong> Hard coding passwords and/or usernames | ||||
in sshexec task can be a serious security hole. Consider using variable | in sshexec task can be a serious security hole. Consider using variable | ||||
substituion and include the password on the command line. For example:<br> | |||||
substitution and include the password on the command line. For example:<br> | |||||
<pre> | <pre> | ||||
<sshexec host="somehost" | <sshexec host="somehost" | ||||
username="${username}" | username="${username}" | ||||
@@ -552,7 +552,7 @@ and the third from a tree rooted at C:\dev\buildtest\co\src\java all to a tree r | |||||
<h3>Description</h3> | <h3>Description</h3> | ||||
Creates a view label in StarTeam at the specified view. The label will be classified by StarTeam as a "build label". This task will fail if there already exexists in <i>viewname</i> a label with the same name as the <i>label</i> parameter. | |||||
Creates a view label in StarTeam at the specified view. The label will be classified by StarTeam as a "build label". This task will fail if there already exists in <i>viewname</i> a label with the same name as the <i>label</i> parameter. | |||||
<h3>Parameters</h3> | <h3>Parameters</h3> | ||||
See also <A href="#common-params">the required common StarTeam parameters</A>.<br></br> | See also <A href="#common-params">the required common StarTeam parameters</A>.<br></br> | ||||
@@ -686,7 +686,7 @@ See also <A href="#common-params">the required common StarTeam parameters</A>.<b | |||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
<td valign="top">asofdate</td> | <td valign="top">asofdate</td> | ||||
<td valign="top">List files, dates, and statusess as of this date. | |||||
<td valign="top">List files, dates, and statuses as of this date. | |||||
The date must be formatted in ISO8601 datetime | The date must be formatted in ISO8601 datetime | ||||
(<code>yyyy-MM-dd'T'HH:mm:ss</code>), ISO8601 | (<code>yyyy-MM-dd'T'HH:mm:ss</code>), ISO8601 | ||||
date(<code>yyyy-MM-dd</code>) or a user-defined SimpleDateFormat | date(<code>yyyy-MM-dd</code>) or a user-defined SimpleDateFormat | ||||
@@ -97,7 +97,7 @@ set of links to record, or a set of property files to create links from. </p> | |||||
</pre> | </pre> | ||||
<p><strong>Java 1.2 and earlier:</strong> Due to limitations on executing system | <p><strong>Java 1.2 and earlier:</strong> Due to limitations on executing system | ||||
level comands in Java versions earlier than 1.3 this task may have difficulty | |||||
level commands in Java versions earlier than 1.3 this task may have difficulty | |||||
operating with a relative path in ANT_HOME. The typical symptom is an | operating with a relative path in ANT_HOME. The typical symptom is an | ||||
IOException where ant can't find /some/working/directory${ANT_HOME}/bin/antRun | IOException where ant can't find /some/working/directory${ANT_HOME}/bin/antRun | ||||
or something similar. The workaround is to change your ANT_HOME environment | or something similar. The workaround is to change your ANT_HOME environment | ||||
@@ -109,7 +109,7 @@ set of links to record, or a set of property files to create links from. </p> | |||||
absolute paths. On non-unix systems this may cause false positives. | absolute paths. On non-unix systems this may cause false positives. | ||||
Furthermore, any operating system on which the command | Furthermore, any operating system on which the command | ||||
<code>ln -s <linkname> <resourcename></code> is not a valid | <code>ln -s <linkname> <resourcename></code> is not a valid | ||||
command on the comand line will not be able to use action="single" or | |||||
command on the command line will not be able to use action="single" or | |||||
action="recreate". Action="record" and action=delete should still work. Finally, | action="recreate". Action="record" and action=delete should still work. Finally, | ||||
the lack of support for symlinks in Java means that all links are recorded as | the lack of support for symlinks in Java means that all links are recorded as | ||||
links to the <strong>canonical</strong> resource name. Therefore the link: | links to the <strong>canonical</strong> resource name. Therefore the link: | ||||
@@ -10,7 +10,7 @@ | |||||
<h2><a name="test">Test</a></h2> | <h2><a name="test">Test</a></h2> | ||||
<h3>Description</h3> | <h3>Description</h3> | ||||
<p>This is a primitive task to execute a unit test in the org.apache.testlet framework.</p> | <p>This is a primitive task to execute a unit test in the org.apache.testlet framework.</p> | ||||
<p><strong>This task is deprectated as the Testlet framework has been | |||||
<p><strong>This task is deprecated as the Testlet framework has been | |||||
abandoned in favor of JUnit by the Avalon community.</strong></p> | abandoned in favor of JUnit by the Avalon community.</strong></p> | ||||
<p><strong>Note:</strong> This task depends on external libraries not included | <p><strong>Note:</strong> This task depends on external libraries not included | ||||
in the Ant distribution. See <a href="../install.html#librarydependencies"> | in the Ant distribution. See <a href="../install.html#librarydependencies"> | ||||
@@ -244,7 +244,7 @@ project.</p> | |||||
<tr> | <tr> | ||||
<td>version</td> | <td>version</td> | ||||
<td>An existing file or project version to label. By default the current | <td>An existing file or project version to label. By default the current | ||||
version is labelled.</td> | |||||
version is labeled.</td> | |||||
<td>No</td> | <td>No</td> | ||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
@@ -15,7 +15,7 @@ Tested only on Weblogic 4.5.1 - NT4.0 and Solaris 5.7,5.8<br> | |||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
<td>src</td> | <td>src</td> | ||||
<td>oot of source tree for JSP, ie, the document root for your weblogic server</td> | |||||
<td>root of source tree for JSP, ie, the document root for your weblogic server</td> | |||||
<td>Yes</td> | <td>Yes</td> | ||||
</tr> | </tr> | ||||
<tr> | <tr> | ||||
@@ -79,7 +79,7 @@ http://java.sun.com/j2se/1.3/docs/guide/extensions/versioning.html</a>.</p> | |||||
implementationURL="http://somewhere.com/myExt.jar"/> | implementationURL="http://somewhere.com/myExt.jar"/> | ||||
</pre></blockquote> | </pre></blockquote> | ||||
<p>Fully specifiec extension object.</p> | |||||
<p>Fully specific extension object.</p> | |||||
<blockquote><pre> | <blockquote><pre> | ||||
<extension id="e1" | <extension id="e1" | ||||