Browse Source
- Applied manual patches supplied by Daniel Martin <dtmartin24@home.com>
- Fixed some other places too. git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@269675 13f79535-47bb-0310-9956-ffa450edef68master
Nico Seessle
24 years ago
37 changed files with 192 additions and 229 deletions
Split View
Diff Options
-
+0 -1docs/manual/CoreTasks/available.html
-
+1 -1docs/manual/CoreTasks/cvspass.html
-
+2 -2docs/manual/CoreTasks/dependset.html
-
+1 -1docs/manual/CoreTasks/jar.html
-
+1 -1docs/manual/CoreTasks/javac.html
-
+3 -3docs/manual/CoreTasks/javadoc.html
-
+1 -1docs/manual/CoreTasks/overview.html
-
+1 -1docs/manual/CoreTasks/parallel.html
-
+6 -6docs/manual/CoreTasks/recorder.html
-
+1 -1docs/manual/CoreTasks/sequential.html
-
+1 -1docs/manual/CoreTasks/tar.html
-
+3 -3docs/manual/CoreTasks/tstamp.html
-
+1 -1docs/manual/CoreTasks/zip.html
-
+5 -7docs/manual/Integration/Antidote.html
-
+2 -3docs/manual/Integration/VAJAntTool.html
-
+3 -3docs/manual/OptionalTasks/BorlandEJBTasks.html
-
+2 -2docs/manual/OptionalTasks/BorlandGenerateClient.html
-
+3 -3docs/manual/OptionalTasks/dotnet.html
-
+13 -16docs/manual/OptionalTasks/ejb.html
-
+0 -1docs/manual/OptionalTasks/icontract.html
-
+3 -5docs/manual/OptionalTasks/jdepend.html
-
+4 -4docs/manual/OptionalTasks/jjtree.html
-
+10 -12docs/manual/OptionalTasks/jpcoverage.html
-
+11 -11docs/manual/OptionalTasks/junit.html
-
+3 -3docs/manual/OptionalTasks/junitreport.html
-
+7 -12docs/manual/OptionalTasks/maudit.html
-
+1 -1docs/manual/OptionalTasks/mimemail.html
-
+9 -11docs/manual/OptionalTasks/mmetrics.html
-
+5 -6docs/manual/OptionalTasks/mparse.html
-
+2 -2docs/manual/OptionalTasks/native2ascii.html
-
+67 -81docs/manual/OptionalTasks/pvcstask.html
-
+2 -3docs/manual/OptionalTasks/starteam.html
-
+7 -11docs/manual/OptionalTasks/wljspc.html
-
+3 -1docs/manual/coretasklist.html
-
+2 -2docs/manual/dirtasks.html
-
+3 -3docs/manual/install.html
-
+3 -3docs/manual/using.html
+ 0
- 1
docs/manual/CoreTasks/available.html
View File
| @@ -104,7 +104,6 @@ if the directory <code>/usr/local/lib</code> is found.</p> | |||
| <p>sets the <code>jaxp11.present</code> property to the value "true" | |||
| if the class <code>javax.xml.transform.Transformer</code> is found in the classpath referenced by <code>jaxp</code> (in this case, <code>./lib/jaxp11/jaxp.jar</code>). | |||
| </p> | |||
| <p> | |||
| <pre> | |||
| <available property="have.extras" resource="extratasks.properties"> | |||
| <classpath> | |||
+ 1
- 1
docs/manual/CoreTasks/cvspass.html
View File
| @@ -9,7 +9,7 @@ | |||
| <h2><a name="cvs">cvspass</a></h2> | |||
| <h3>Description</h3> | |||
| <p>Adds entries to a .cvspass file. Adding entries to this file has the same affect as a cvs login command. | |||
| <p>Adds entries to a .cvspass file. Adding entries to this file has the same affect as a cvs login command.</p> | |||
| <h3>Parameters</h3> | |||
| <table border="1" cellpadding="2" cellspacing="0"> | |||
| <tr> | |||
+ 2
- 2
docs/manual/CoreTasks/dependset.html
View File
| @@ -109,14 +109,14 @@ filelists, and if any are older, they are all deleted. | |||
| <p> | |||
| In this example derived HTML files in the ${output.dir} directory | |||
| will be removed if any are out-of-date with respect to: | |||
| will be removed if any are out-of-date with respect to:</p> | |||
| <ol> | |||
| <li>the DTD of their source XML files</li> | |||
| <li>a common DTD (imported by the main DTD)</li> | |||
| <li>a subordinate XSLT stylesheet (imported by the main stylesheet), or</li> | |||
| <li>the buildfile</li> | |||
| </ol> | |||
| </p> | |||
| <p> | |||
| If any of the source files in the above example does not exist, all | |||
| target files will also be removed. To ignore missing source files instead, | |||
+ 1
- 1
docs/manual/CoreTasks/jar.html
View File
| @@ -37,7 +37,7 @@ You should not include <samp>META-INF/MANIFEST.MF</samp> in your set of files.</ | |||
| JAR file already exists. When set to <code>yes</code>, the JAR file is | |||
| updated with the files specified. When set to <code>no</code> (the | |||
| default) the JAR file is overwritten. An example use of this is | |||
| provided in the <a href="zip.html">Zip task documentation</a>. | |||
| provided in the <a href="zip.html">Zip task documentation</a>.</p> | |||
| <p>The <code>whenempty</code> parameter controls what happens when no files match. | |||
| If <code>create</code> (the default), the JAR is created anyway with only a manifest. | |||
| If <code>skip</code>, the JAR is not created and a warning is issued. | |||
+ 1
- 1
docs/manual/CoreTasks/javac.html
View File
| @@ -304,7 +304,7 @@ properties prior to invoking the task. The ant developers are aware that | |||
| this is ugly and inflexible -expect a better solution in the future. All | |||
| the options are boolean, and must be set to "true" or "yes" to be | |||
| interpreted as anything other than false; by default | |||
| build.compiler.warnings is "true" while all others are "false" | |||
| build.compiler.warnings is "true" while all others are "false"</p> | |||
| <table border="1" cellpadding="2" cellspacing="0"> | |||
| <tr> | |||
+ 3
- 3
docs/manual/CoreTasks/javadoc.html
View File
| @@ -396,9 +396,9 @@ the second one a colon delimited list of packages.</p> | |||
| contains a comma or a space character, using <a | |||
| href="#groupelement">nested group elements</a> is highly | |||
| recommended.</p> | |||
| <p>E.g., | |||
| <p>E.g., </p> | |||
| <pre> group="XSLT_Packages org.apache.xalan.xslt*,XPath_Packages org.apache.xalan.xpath*" | |||
| </pre></p> | |||
| </pre> | |||
| <h3>Parameters specified as nested elements</h3> | |||
| @@ -519,7 +519,7 @@ arguments.</p> | |||
| <p>The title may be specified as a nested <code><title></code> element | |||
| with text contents, and the packages may be listed with nested | |||
| <code><package></code> elements as for the main task. | |||
| <code><package></code> elements as for the main task.</p> | |||
| <h4>doclet</h4> | |||
| <p>The doclet nested element is used to specify the doclet that javadoc will | |||
+ 1
- 1
docs/manual/CoreTasks/overview.html
View File
| @@ -93,7 +93,7 @@ file, a directory, a class in the classpath, or a JVM system resource.</p></td> | |||
| <td><a href="delete.html">Delete</a></td> | |||
| <td><p>Deletes either a single file, all files in a specified directory | |||
| and its sub-directories, or a set of files specified by one or more | |||
| <a href="../CoreTypes/fileset.html">FileSet</a>s.</td> | |||
| <a href="../CoreTypes/fileset.html">FileSet</a>s.</p></td> | |||
| </tr> | |||
| <tr valign="top"> | |||
+ 1
- 1
docs/manual/CoreTasks/parallel.html
View File
| @@ -12,7 +12,7 @@ | |||
| <p>Parallel is a container task - it can contain other Ant tasks. Each nested | |||
| task within the parallel task will be executed in its own thread. </p> | |||
| <p>Parallel tasks have a number of uses in an Ant build file including: | |||
| <p>Parallel tasks have a number of uses in an Ant build file including:</p> | |||
| <ul> | |||
| <li>Taking advantage of available processing resources to reduce build time</li> | |||
| <li>Testing servers, where the server can be run in one thread and the test | |||
+ 6
- 6
docs/manual/CoreTasks/recorder.html
View File
| @@ -10,7 +10,7 @@ | |||
| <h2><a name="log">Record</a></h2> | |||
| <h3>Description</h3> | |||
| <p>A recorder is a listener to the current build process that records the | |||
| output to a file. | |||
| output to a file.</p> | |||
| <p>Several recorders can exist at the same time. Each recorder is | |||
| associated with a file. The filename is used as a unique identifier for | |||
| @@ -18,11 +18,11 @@ the recorders. The first call to the recorder task with an unused filename | |||
| will create a recorder (using the parameters provided) and add it to the | |||
| listeners of the build. All subsequent calls to the recorder task using | |||
| this filename will modify that recorders state (recording or not) or other | |||
| properties (like logging level). | |||
| properties (like logging level).</p> | |||
| <p>Some technical issues: the file's print stream is flushed for "finished" | |||
| events (buildFinished, targetFinished and taskFinished), and is closed on | |||
| a buildFinished event. | |||
| a buildFinished event.</p> | |||
| <h3>Parameters</h3> | |||
| <table border="1" cellpadding="2" cellspacing="0"> | |||
| @@ -66,7 +66,7 @@ a buildFinished event. | |||
| <h3>Examples</h3> | |||
| <p>The following build.xml snippet is an example of how to use the recorder | |||
| to record just the <code><javac></code> task: | |||
| to record just the <code><javac></code> task:</p> | |||
| <pre> | |||
| ... | |||
| <compile > | |||
| @@ -80,7 +80,7 @@ to record just the <code><javac></code> task: | |||
| <p>The following two calls to <code><record></code> set up two | |||
| recorders: one to file "records-simple.log" at logging level <code>info</code> | |||
| (the default) and one to file "ISO.log" using logging level of | |||
| <code>verbose</code>. | |||
| <code>verbose</code>.</p> | |||
| <pre> | |||
| ... | |||
| <record name="records-simple.log" /> | |||
| @@ -90,7 +90,7 @@ recorders: one to file "records-simple.log" at logging level <code>inf | |||
| <h3>Notes</h3> | |||
| <p>There is some functionality that I would like to be able to add in the | |||
| future. They include things like the following: | |||
| future. They include things like the following:</p> | |||
| <table border="1" cellpadding="2" cellspacing="0"> | |||
| <tr> | |||
| <td valign="top"><b>Attribute</b></td> | |||
+ 1
- 1
docs/manual/CoreTasks/sequential.html
View File
| @@ -30,7 +30,7 @@ sequential task.</p> | |||
| </parallel> | |||
| </pre> | |||
| <p>This example shows how the sequential task is used to execute three tasks in | |||
| sequence, while another task is being executed in a separate thread. | |||
| sequence, while another task is being executed in a separate thread. </p> | |||
| <hr> | |||
| <p align="center">Copyright © 2000,2001 Apache Software Foundation. All rights | |||
+ 1
- 1
docs/manual/CoreTasks/tar.html
View File
| @@ -66,7 +66,7 @@ the limit.</p> | |||
| <td valign="top">Determines how long files (>100 chars) are to be | |||
| handled. Allowable values are "truncate", "fail", | |||
| "warn", "omil" and "gnu". Default is | |||
| "warn". | |||
| "warn".</td> | |||
| <td valign="top" align="center">No</td> | |||
| </tr> | |||
| <tr> | |||
+ 3
- 3
docs/manual/CoreTasks/tstamp.html
View File
| @@ -14,12 +14,12 @@ | |||
| properties in the current project. The <code>DSTAMP</code> property is in the | |||
| format "yyyymmdd", <code>TSTAMP</code> is in the | |||
| format "hhmm", and <code>TODAY</code> is in the | |||
| format "month day year". | |||
| format "month day year".</p> | |||
| <p>These properties can be used in the build-file, for instance, to create | |||
| time-stamped filenames, or used to replace placeholder tags inside documents | |||
| to indicate, for example, the release date. The best place for this task is | |||
| probably in an initialization target. | |||
| probably in an initialization target.</p> | |||
| <h3>Parameters</h3> | |||
| <table border="1" cellpadding="2" cellspacing="0"> | |||
| @@ -108,7 +108,7 @@ and <code>TODAY</code> properties according to the default formats.</p> | |||
| <p> | |||
| sets the standard properties as well as the property | |||
| <code>TODAY_UK</code> with the date/time pattern "d-MMMM-yyyy" | |||
| using English locale (eg. 21-May-2001). | |||
| using English locale (eg. 21-May-2001).</p> | |||
| <pre> | |||
| <tstamp> | |||
+ 1
- 1
docs/manual/CoreTasks/zip.html
View File
| @@ -37,7 +37,7 @@ only reflect the relative paths of files <i>within</i> each fileset. The Zip tas | |||
| ZIP file already exists. When set to <code>yes</code>, the ZIP file is | |||
| updated with the files specified. (New files are added; old files are | |||
| replaced with the new versions.) When set to <code>no</code> (the | |||
| default) the ZIP file is overwritten. | |||
| default) the ZIP file is overwritten.</p> | |||
| <p>The <code>whenempty</code> parameter controls what happens when no files match. | |||
| If <code>skip</code> (the default), the ZIP is not created and a warning is issued. | |||
| If <code>fail</code>, the ZIP is not created and the build is halted with an error. | |||
+ 5
- 7
docs/manual/Integration/Antidote.html
View File
| @@ -31,7 +31,7 @@ | |||
| <H2>Status</H2> | |||
| <P>Antidote is still in the early stages of development, but does | |||
| have a set of usable features, including: | |||
| have a set of usable features, including:</p> | |||
| <UL> | |||
| <LI>Reading Ant build files.</LI> | |||
| <LI>Selecting targets and executing them.</LI> | |||
| @@ -39,9 +39,8 @@ | |||
| <LI>Modification of (some) build file components.</LI> | |||
| <LI>Saving modified build file.</LI> | |||
| </UL> | |||
| </P> | |||
| <P>Current development tasks include: | |||
| <P>Current development tasks include:</p> | |||
| <UL> | |||
| <LI>A more complete set of target and task editing | |||
| capabilities.</LI> | |||
| @@ -49,7 +48,6 @@ | |||
| existing code bases.</LI> | |||
| <LI>Better build progress monitoring.</LI> | |||
| </UL> | |||
| </P> | |||
| <P>The Antidote source distribution comes with requirements and | |||
| design documentation that better cover the details of application | |||
| @@ -62,7 +60,7 @@ | |||
| <P>The source code for Antidote is located in a separate Module | |||
| (<a href="http://cvs.apache.org/viewcvs/jakarta-ant-antidote/">jakarta-ant-antidote</a>) in CVS. | |||
| All the existing documentation can | |||
| be found there where new contributors should read: | |||
| be found there where new contributors should read:</p> | |||
| <UL> | |||
| <LI><A HREF="http://cvs.apache.org/viewcvs/~checkout~/jakarta-ant-antidote/docs/developer/design/design-overview.html">Design Overview</A></LI> | |||
| <LI><A HREF="http://cvs.apache.org/viewcvs/~checkout~/jakarta-ant-antidote/docs/developer/design/gui-requirements.html">Feature List</A></LI> | |||
| @@ -75,11 +73,11 @@ | |||
| HREF="http://jakarta.apache.org/site/mail.html">jakarta-ant | |||
| mailing list</A>. The application infrastructure is fairly | |||
| complete, but there are almost unlimited opportunities for feature | |||
| contributions. | |||
| contributions.</p> | |||
| <P>Aspiring contributors new to the Jakarta Project should | |||
| (carefully) read the following for details on the contribution | |||
| process: | |||
| process:</p> | |||
| <UL> | |||
| <LI><A | |||
| HREF="http://jakarta.apache.org/site/getinvolved.html">Get | |||
+ 2
- 3
docs/manual/Integration/VAJAntTool.html
View File
| @@ -166,7 +166,7 @@ FileSets</a>. </p> | |||
| </tr> | |||
| <tr valign="Top"> | |||
| <td valign="Top">defaultexcludes </td> | |||
| <td valign="Top">use default excludes when exporting (default: "yes") | |||
| <td valign="Top">use default excludes when exporting (default: "yes")</td> | |||
| <td valign="Top" align="Center">no</td> | |||
| </tr> | |||
| </tbody> | |||
| @@ -561,7 +561,7 @@ Project name at the beginning of the "includes" parameter. | |||
| <p><b>Q: When I import Ant into my Workspace, I get Problems reported. Can I | |||
| ignore them?</b><br> | |||
| A: It depends on the problems reported, and what you want to do with Ant. | |||
| Problems you can't ignore: | |||
| Problems you can't ignore:</p> | |||
| <ul> | |||
| <li>Classes from javax.xml.parser missing - install a compatible parser | |||
| (see <a href="#installation">installation</a>) | |||
| @@ -570,7 +570,6 @@ Problems you can't ignore: | |||
| Utility feature (see <a href="#installation">installation</a>). | |||
| </li> | |||
| </ul> | |||
| </p> | |||
| <p><b>Q: Why is the task name vajload when the class is called VAJLoadProjects?</b><br> | |||
| A: At the moment this task can load only project versions. This is reflected | |||
+ 3
- 3
docs/manual/OptionalTasks/BorlandEJBTasks.html
View File
| @@ -9,11 +9,11 @@ | |||
| <h2><a name="log">BorlandDeploy</a>Tool</h2> | |||
| <h3>Description</h3> | |||
| <p>The BorlandDeployTool is a vendor specific nested element for the Ejbjar optional task. | |||
| <p>The BorlandDeployTool is a vendor specific nested element for the Ejbjar optional task.</p> | |||
| <p>BorlandDeploymentTool is dedicated to the Borland Application Server 4.5. It | |||
| generates and compiles the stubs and skeletons for all ejb described into the | |||
| Deployment Descriptor, builds the jar file including the support files and | |||
| verify whether the produced jar is valid or not. | |||
| verify whether the produced jar is valid or not.</p> | |||
| <h3>Borland element</h3> | |||
| <table border="1" cellpadding="2" cellspacing="0"> | |||
| <tr> | |||
| @@ -76,7 +76,7 @@ | |||
| <h3>Examples</h3> | |||
| <p>The following build.xml snippet is an example of how to use Borland element | |||
| into the ejbjar task | |||
| into the ejbjar task</p> | |||
| <pre> <ejbjar srcdir="${build.classes}" basejarname="vsmp" descriptordir="${rsc.dir}/hrmanager"> | |||
| <borland destdir="lib" verify="on" generateclient="on"> | |||
| <classpath refid="classpath" /> | |||
+ 2
- 2
docs/manual/OptionalTasks/BorlandGenerateClient.html
View File
| @@ -11,7 +11,7 @@ | |||
| <h3>Description</h3> | |||
| <p>The BorlandGenerateClient is a task dedicated to Borland Application Server | |||
| v 4.5. It offers to generate the client jar file corresponding to an ejb jar | |||
| file. | |||
| file.</p> | |||
| <h3>Parameters</h3> | |||
| <table border="1" cellpadding="2" cellspacing="0"> | |||
| <tr> | |||
| @@ -47,7 +47,7 @@ | |||
| <h3>Examples</h3> | |||
| <p>The following build.xml snippet is an example of how to use Borland element | |||
| into the ejbjar task using the java mode. | |||
| into the ejbjar task using the java mode.</p> | |||
| <pre> | |||
| <blgenclient ejbjar="lib/secutest-ejb.jar" clientjar="lib/client.jar" debug="true" mode="java"> | |||
| <classpath> | |||
+ 3
- 3
docs/manual/OptionalTasks/dotnet.html
View File
| @@ -120,9 +120,9 @@ version crimson.jar and jaxp.jar.</li> | |||
| This is the beta-2 revision of the tasks. | |||
| <ol> | |||
| <li>ILASM: pulled the owner attribute, added keyfile for giving binaries a strong name | |||
| (MD5 hash of the checksum) | |||
| <li>CSC: added win32res , noConfig, utf8output, fullpaths | |||
| <li>CSC: | |||
| (MD5 hash of the checksum)</li> | |||
| <li>CSC: added win32res , noConfig, utf8output, fullpaths</li> | |||
| <li>CSC: </li> | |||
| </ol> | |||
| <h4>Version 0.3</h4> | |||
+ 13
- 16
docs/manual/OptionalTasks/ejb.html
View File
| @@ -198,7 +198,7 @@ task will also attempt to locate the EJB stubs and skeletons in this directory. | |||
| If found, the timestamps on the stubs and skeletons will be checked to | |||
| ensure they are up to date. Only if these files cannot be found or if they | |||
| are out of date will the iAS ejbc utility be called to generate new stubs | |||
| and skeletons. | |||
| and skeletons.</p> | |||
| <h3> | |||
| Parameters:</h3> | |||
| @@ -222,7 +222,7 @@ Parameters:</h3> | |||
| <tr> | |||
| <td VALIGN=TOP>iasdescriptor</td> | |||
| <td VALIGN=TOP>iAS-specific EJB XML descriptor (typically titled "ias-ejb-jar.xml).</td> | |||
| <td VALIGN=TOP>iAS-specific EJB XML descriptor (typically titled "ias-ejb-jar.xml").</td> | |||
| <td ALIGN=CENTER VALIGN=TOP>Yes</td> | |||
| </tr> | |||
| @@ -529,7 +529,7 @@ include: </p> | |||
| <li>Borland Application Server 4.5</li> | |||
| <li>iPlanet Application Server 6.0</li> | |||
| <li>Jboss 2.1 and above</li> | |||
| <li>Weblogic 5.1/6.0 session/entity beans using the weblogic.ejbc tool | |||
| <li>Weblogic 5.1/6.0 session/entity beans using the weblogic.ejbc tool</li> | |||
| <li>TOPLink for WebLogic 2.5.1-enabled entity beans</li> | |||
| </ul> | |||
| @@ -716,9 +716,8 @@ Each vendor-specific nested element controls the generation of a deployable jar | |||
| specific to that vendor's EJB container. The parameters for each supported | |||
| deployment element are detailed here. | |||
| <a name="ejbjar_jboss"> | |||
| <h3>Jboss element</h3> | |||
| </a> | |||
| <h3><a name="ejbjar_jboss">Jboss element</a></h3> | |||
| <p>The jboss element searches for the jboss specific deployment descriptors and adds them | |||
| to the final ejb jar file. Jboss has two deployment descriptors jboss.xml and jaws.xml | |||
| @@ -764,9 +763,8 @@ not require compilation of additional stubs and skeletons.</p> | |||
| </tr> | |||
| </table> | |||
| <a name="ejbjar_weblogic"> | |||
| <h3>Weblogic element</h3> | |||
| </a> | |||
| <h3><a name="ejbjar_weblogic">Weblogic element</a></h3> | |||
| <p>The weblogic element is used to control the weblogic.ejbc compiler for | |||
| generating weblogic EJB jars. Prior to Ant 1.3, the method of locating CMP | |||
| @@ -1044,7 +1042,7 @@ This will create only one TOPLink-enabled ejb jar file - 'Address.jar'.</p> | |||
| </pre> | |||
| <p>This final example shows how you would set-up ejbjar under Weblogic 6.0. It also shows the use of the | |||
| <support> element to add support files | |||
| <support> element to add support files</p> | |||
| <pre> | |||
| <ejbjar descriptordir="${dd.dir}" srcdir="${build.classes.server}"> | |||
| @@ -1067,9 +1065,8 @@ This will create only one TOPLink-enabled ejb jar file - 'Address.jar'.</p> | |||
| </ejbjar> | |||
| </pre> | |||
| <a name="ejbjar_iplanet"> | |||
| <h3>iPlanet Application Server (iAS) element</h3> | |||
| </a> | |||
| <h3><a name="ejbjar_iplanet">iPlanet Application Server (iAS) element</a></h3> | |||
| The <iplanet> nested element is used to build iAS-specific stubs and | |||
| skeletons and construct a JAR file which may be deployed to the iPlanet | |||
| @@ -1084,11 +1081,11 @@ EJB descriptor file named ejb/Account-ias-ejb-jar.xml (if it isn't found, | |||
| the task will fail) and a JAR file named ejb/Account.jar will be written | |||
| in the destination directory. Note that when the EJB descriptors | |||
| are added to the JAR file, they are automatically renamed META-INF/ejb-jar.xml | |||
| and META-INF/ias-ejb-jar.xml. | |||
| and META-INF/ias-ejb-jar.xml.</p> | |||
| <p>Of course, this naming behavior can be modified by specifying attributes | |||
| in the ejbjar task (for example, basejarname, basenameterminator, and flatdestdir) | |||
| as well as the iplanet element (for example, suffix). Refer to the | |||
| appropriate documentation for more details. | |||
| appropriate documentation for more details.</p> | |||
| <h3> | |||
| Parameters:</h3> | |||
| @@ -1166,7 +1163,7 @@ If omitted, it defaults to ".jar". </td> | |||
| </table> | |||
| <p>As noted above, the iplanet element supports additional <classpath> | |||
| nested elements. | |||
| nested elements.</p> | |||
| <h3> | |||
| Examples</h3> | |||
| This example demonstrates the typical use of the <iplanet> nested element. | |||
+ 0
- 1
docs/manual/OptionalTasks/icontract.html
View File
| @@ -44,7 +44,6 @@ Instruments Java classes with <a href="http://www.reliable-systems.com/tools/">i | |||
| <td valign="top">builddir</td> | |||
| <td valign="top">Indicates where the compiled instrumented classes should go. | |||
| Defaults to the value of instrumentdir. | |||
| </p> | |||
| <em>NOTE:</em> Don't use the same directory for compiled instrumented classes | |||
| and uninstrumented classes. It will break the dependency checking. (Classes will | |||
| not be reinstrumented if you change them).</td> | |||
+ 3
- 5
docs/manual/OptionalTasks/jdepend.html
View File
| @@ -15,9 +15,9 @@ | |||
| <P>Invokes the <a href="http://www.clarkware.com/software/JDepend.html">JDepend</a> parser.</P> | |||
| <P>This parser "traverses a set of Java source file directories and generates design quality metrics for each Java package". | |||
| It allows to "automatically measure the quality of a design in terms of its extensibility, reusability, and maintainability to | |||
| effectively manage and control package dependencies."</P> | |||
| <P>This parser "traverses a set of Java source file directories and generates design quality metrics for each Java package". | |||
| It allows to "automatically measure the quality of a design in terms of its extensibility, reusability, and maintainability to | |||
| effectively manage and control package dependencies."</P> | |||
| <p>Source file directories are defined by nested <code><sourcespath></code>, see <a href="#nested">nested elements</a>.</p> | |||
| @@ -27,8 +27,6 @@ effectively manage and control package dependencies."</P> | |||
| <P>Note: whereas the JDepend tool can be customized to exclude some packages, the current jdepend And Task does not have parameters to allow these exclusions. Read JDepend specific documentation for that purpose.</P> | |||
| <p> | |||
| <h3>Parameters</h3> | |||
| <table BORDER=1 CELLSPACING=0 CELLPADDING=2 > | |||
+ 4
- 4
docs/manual/OptionalTasks/jjtree.html
View File
| @@ -23,11 +23,11 @@ so that ant can find the JavaCC classes. Optionally, you can also set the | |||
| <i>outputdirectory</i> | |||
| to write the generated file to a specific directory. Otherwise jjtree writes | |||
| the generated JavaCC grammar file to the directory containing the JJTree | |||
| grammar file. | |||
| grammar file.</p> | |||
| <p>This task only invokes JJTree if the grammar file is newer than the | |||
| generated JavaCC file. | |||
| <h3> | |||
| Parameters</h3> | |||
| generated JavaCC file.</p> | |||
| <h3>Parameters</h3> | |||
| <table BORDER CELLSPACING=0 CELLPADDING=2 > | |||
| <tr> | |||
+ 10
- 12
docs/manual/OptionalTasks/jpcoverage.html
View File
| @@ -24,7 +24,6 @@ and is not intended as a replacement to the manual. | |||
| </p> | |||
| <h2>Tasks</h2> | |||
| <ul> | |||
| <table border="0" cellspacing="0" cellpadding="3"> | |||
| <tr> | |||
| <td><a href="#jpcoverage">JPCoverage</a></td> | |||
| @@ -39,7 +38,6 @@ and is not intended as a replacement to the manual. | |||
| <td>Create a report from a snapshot</td> | |||
| </tr> | |||
| </table> | |||
| </ul> | |||
| <hr> | |||
| @@ -97,8 +95,8 @@ Perform code covering functions by comparing source code line execution to the p | |||
| <tr> | |||
| <td valign="top">exitprompt</td> | |||
| <td valign="top">Toggles display of the console prompt: "Press Enter to close | |||
| this window." "always": Always displays the prompt. "never": Never displays the | |||
| <td valign="top">Toggles display of the console prompt: "Press Enter to close | |||
| this window." "always": Always displays the prompt. "never": Never displays the | |||
| prompt. "error": Only displays prompt after an error.</td> | |||
| <td align="center" valign="top">No, default is "never"</td> | |||
| </tr> | |||
| @@ -150,7 +148,7 @@ Perform code covering functions by comparing source code line execution to the p | |||
| <h4>classpath</h4> | |||
| <p><code>jpcoverage</code> supports a nested <code><classpath></code> | |||
| element, that represents a <a href="index.html#path">PATH like | |||
| element, that represents a <a href="../using.html#path">PATH like | |||
| structure</a>.</p> | |||
| <h4>jvmarg</h4> | |||
| @@ -169,13 +167,13 @@ attributes, for example:</p> | |||
| would run the coverage on "MyClass" in classic mode VM. | |||
| <p><code><jvmarg></code> allows all attributes described in <a | |||
| href="index.html#arg">Command line arguments</a>.</p> | |||
| href="../using.html#arg">Command line arguments</a>.</p> | |||
| <h4>arg</h4> | |||
| <p> | |||
| Parameters may be passed to the executed class via nested <tt><arg></tt> | |||
| attributes, as described in <a href="index.html#arg">Command line arguments</a>. | |||
| attributes, as described in <a href="../using.html#arg">Command line arguments</a>. | |||
| </p> | |||
| <h4>socket</h4> | |||
| @@ -204,7 +202,7 @@ attributes, as described in <a href="index.html#arg">Command line arguments</a>. | |||
| <h4>filters</h4> | |||
| <p>Defines class/method filters based on pattern matching. | |||
| The syntax is filters is similar to a <a href="index.html#fileset">fileset</a>. | |||
| The syntax is filters is similar to a <a href="../CoreTypes/fileset.html">fileset</a>. | |||
| </p> | |||
| <table border="1" cellpadding="2" cellspacing="0"> | |||
| @@ -348,7 +346,7 @@ same class.</p> | |||
| </table> | |||
| <p> | |||
| <tt>jpcovmerge</tt> collects snapshots using the nested <a href="index.html#fileset"><code><FileSet></code></a> | |||
| <tt>jpcovmerge</tt> collects snapshots using the nested <a href="../CoreTypes/fileset.html"><code><FileSet></code></a> | |||
| element. | |||
| </p> | |||
| @@ -368,7 +366,7 @@ directory <tt>snapshots</tt>. The resulting file will be named <tt>merge.jpc</tt | |||
| <hr> | |||
| <h2>JPCovReport</h2> | |||
| <h2><a name="jpcovreport">JPCovReport</a></h2> | |||
| <h3>Description</h3> | |||
| @@ -425,7 +423,7 @@ Oro</a> in Ant classpath, to run the <tt>reference</tt> feature.</p> | |||
| <h4>sourcepath</h4> | |||
| <p> | |||
| Path to source files can be set via nested sourcepath elements that are <a href="index.html#path">PATH like structures</a>. | |||
| Path to source files can be set via nested sourcepath elements that are <a href="../using.html#path">PATH like structures</a>. | |||
| </p> | |||
| <h4>reference (only applies to format="xml")</h4> | |||
| @@ -456,7 +454,7 @@ the XML report accordingly. In short, it will: | |||
| </h4> | |||
| <p> | |||
| Path to the reference set of files can be set via nested classpath elements that are <a href="index.html#path">PATH like structures</a>. | |||
| Path to the reference set of files can be set via nested classpath elements that are <a href="../using.html#path">PATH like structures</a>. | |||
| </p> | |||
| <h4>filters | |||
+ 11
- 11
docs/manual/OptionalTasks/junit.html
View File
| @@ -97,7 +97,7 @@ structure</a>.</p> | |||
| <h4>jvmarg</h4> | |||
| <p>If fork is enabled, additional parameters may be passed to the new | |||
| VM via nested <code><jvmarg></code> attributes, for example: | |||
| VM via nested <code><jvmarg></code> attributes, for example:</p> | |||
| <pre> | |||
| <junit fork="yes"> | |||
| @@ -106,7 +106,7 @@ VM via nested <code><jvmarg></code> attributes, for example: | |||
| </junit> | |||
| </pre> | |||
| would run the test in a VM without JIT.</p> | |||
| <p>would run the test in a VM without JIT.</p> | |||
| <p><code><jvmarg></code> allows all attributes described in <a | |||
| href="../using.html#arg">Command line arguments</a>.</p> | |||
| @@ -116,7 +116,7 @@ href="../using.html#arg">Command line arguments</a>.</p> | |||
| <p>Use nested <code><sysproperty></code> elements to specify system | |||
| properties required by the class. These properties will be made available | |||
| to the VM during the execution of the test (either ANT's VM or the forked VM). | |||
| The attributes for this element are the same as for <a href="../CoreTasks/exec.html#env">environment variables</a>. | |||
| The attributes for this element are the same as for <a href="../CoreTasks/exec.html#env">environment variables</a>.</p> | |||
| <pre> | |||
| <junit fork="no"> | |||
| @@ -125,7 +125,7 @@ The attributes for this element are the same as for <a href="../CoreTasks/exec.h | |||
| </junit> | |||
| </pre> | |||
| would run the test in ANT's VM and make the <code>basedir</code> property | |||
| <p>would run the test in ANT's VM and make the <code>basedir</code> property | |||
| available to the test.</p> | |||
| @@ -135,7 +135,7 @@ available to the test.</p> | |||
| formats. Output will always be sent to a file unless you set the | |||
| usefile attribute to false, the name of the file is determined by the | |||
| name of the test and can be set by the <code>outfile</code> attribute | |||
| of <code><test></code>. | |||
| of <code><test></code>.</p> | |||
| <p>There are three predefined formatters, one prints the test results | |||
| in XML format, the other emit plain text. The formatter named | |||
| @@ -317,29 +317,29 @@ generates a test class name for each file that ends in | |||
| <h3>Examples</h3> | |||
| <p><pre> | |||
| <pre> | |||
| <junit> | |||
| <test name="my.test.TestCase" /> | |||
| </junit> | |||
| </pre> | |||
| Runs the test defined in <code>my.test.TestCase</code> in the same | |||
| <p>Runs the test defined in <code>my.test.TestCase</code> in the same | |||
| VM. No output will be generated unless the test fails.</p> | |||
| <p><pre> | |||
| <pre> | |||
| <junit printsummary="yes" fork="yes" haltonfailure="yes"> | |||
| <formatter type="plain" /> | |||
| <test name="my.test.TestCase" /> | |||
| </junit> | |||
| </pre> | |||
| Runs the test defined in <code>my.test.TestCase</code> in a | |||
| <p>Runs the test defined in <code>my.test.TestCase</code> in a | |||
| separate VM. At the end of the test a single line summary will be | |||
| printed. A detailed report of the test can be found in | |||
| <code>TEST-my.test.TestCase.txt</code>. The build process will be | |||
| stopped if the test fails.</p> | |||
| <p><pre> | |||
| <pre> | |||
| <junit printsummary="yes" haltonfailure="yes"> | |||
| <classpath> | |||
| <pathelement location="${build.tests}" /> | |||
| @@ -361,7 +361,7 @@ stopped if the test fails.</p> | |||
| </junit> | |||
| </pre> | |||
| Runs <code>my.test.TestCase</code> in the same VM (ignoring the | |||
| <p>Runs <code>my.test.TestCase</code> in the same VM (ignoring the | |||
| given CLASSPATH), only a warning is printed if this test fails. In | |||
| addition to the plain text test results, for this test a XML result | |||
| will be output to <code>result.xml</code>.</p> | |||
+ 3
- 3
docs/manual/OptionalTasks/junitreport.html
View File
| @@ -11,13 +11,13 @@ a stylesheet on the resulting merged document to provide a browsable report of | |||
| the testcases results. | |||
| <h3>Requirements</h3> | |||
| <p>The task will run with either <a href="http://xml.apache.org/xalan-j/">Xalan 2.x</a> | |||
| or <a href="http://xml.apache.org/dist/xalan-j/old/xalan-j_1_2_2.zip">Xalan 1.2.2</a>. | |||
| or <a href="http://xml.apache.org/dist/xalan-j/old/xalan-j_1_2_2.zip">Xalan 1.2.2</a>.</p> | |||
| <p> | |||
| Note:<i>For a framed format Xalan 1.2.2 will need Xerces(xerces.jar) as well as BSF(bsf.jar) | |||
| that can be found in the distribution archive. Xerces will need to be before any other | |||
| parser (such as the shipped crimson). It is *highly* recommended to use Xalan2 instead | |||
| because Xalan1 is no more supported. | |||
| </i> | |||
| </i></p> | |||
| <h3>Parameters</h3> | |||
| <table border="1" cellpadding="2" cellspacing="0"> | |||
| <tr> | |||
| @@ -41,7 +41,7 @@ because Xalan1 is no more supported. | |||
| <h3><a name="nested">Nested Elements</a></h3> | |||
| <h4>fileset</h4> | |||
| <p><code>junitreport</code> collects individual xml files generated by the JUnit | |||
| task using the nested <a href="index.html#fileset"><code><FileSet></code></a> | |||
| task using the nested <a href="../CoreTypes/fileset.html"><code><FileSet></code></a> | |||
| element.</p> | |||
| <h4>report</h4> | |||
| <p>Generate a browsable report based on the document created by the merge.</p> | |||
+ 7
- 12
docs/manual/OptionalTasks/maudit.html
View File
| @@ -76,20 +76,20 @@ An evaluation version is available at <a href="http://www.webgain.com/products/q | |||
| <h3>Nested elements</h3> | |||
| <h4>jvmarg</h4> | |||
| <p>Additional parameters may be passed to the VM via nested <code><jvmarg></code> | |||
| attributes. <code><jvmarg></code> allows all attributes described in <a href="index.html#arg">Command | |||
| attributes. <code><jvmarg></code> allows all attributes described in <a href="../using.html#arg">Command | |||
| line arguments</a>.</p> | |||
| <h4>classpath</h4> | |||
| <p>Sets class path (also source path unless one explicitly set). Overrides | |||
| METAPATH/CLASSPATH environment variables. The <tt>classpath</tt> element represents a <a href="../#path">PATH like | |||
| METAPATH/CLASSPATH environment variables. The <tt>classpath</tt> element represents a <a href="../using.html#path">PATH like | |||
| structure</a>.</p> | |||
| <h4>sourcepath</h4> | |||
| <p>Sets source path. Overrides the SOURCEPATH environment variable. The <tt>sourcepath</tt> element represents a <a href="../coreTypes/fileset.htmlindex.html#path">PATH like | |||
| <p>Sets source path. Overrides the SOURCEPATH environment variable. The <tt>sourcepath</tt> element represents a <a href="../using.html#path">PATH like | |||
| structure</a>.</p> | |||
| <h4>sourcepath</h4> | |||
| <p>Sets the search path to use as the use domain when looking for unused global declarations. The <tt>searchpath</tt> element represents a <a href="../coreTypes/fileset.htmlindex.html#path">PATH like | |||
| <p>Sets the search path to use as the use domain when looking for unused global declarations. The <tt>searchpath</tt> element represents a <a href="../using.html#path">PATH like | |||
| structure</a>.</p> | |||
| <h4>fileset</h4> | |||
| <p>Sets the Java files to audit via a <a href="index.html#fileset">FILESET</a> structure. | |||
| <p>Sets the Java files to audit via a <a href="../CoreTypes/fileset.html">FILESET</a> structure. | |||
| Whatever the filter is, only the files that ends with <i>.java</i> will be included for processing. | |||
| Note that the base directory used for the fileset MUST be the root of the source files otherwise | |||
| package names deduced from the file path will be incorrect. | |||
| @@ -128,10 +128,5 @@ in the current directory), it can be run in Ant as follows: | |||
| </java> | |||
| </pre> | |||
| <hr> | |||
| <hr> | |||
| </body> | |||
| </html> | |||
+ 1
- 1
docs/manual/OptionalTasks/mimemail.html
View File
| @@ -10,7 +10,7 @@ | |||
| <h2><a name="mimemail">MimeMail</a></h2> | |||
| <h3>Description</h3> | |||
| <p>Sends SMTP mail with MIME attachments. If no attachments | |||
| are needed, use the built-in <a href="http://jakarta.apache.org/ant/manual/CoreTasks/mail.html">Mail</a> | |||
| are needed, use the built-in <a href="../CoreTasks/mail.html">Mail</a> | |||
| task. <a href="http://java.sun.com/products/javamail/index.html">JavaMail</a> | |||
| and <a href="http://java.sun.com/products/javabeans/glasgow/jaf.html">Java | |||
| Activation Framework</a> are required for this task.</p> | |||
+ 9
- 11
docs/manual/OptionalTasks/mmetrics.html
View File
| @@ -19,7 +19,7 @@ An evaluation version is available at <a href="http://www.webgain.com/products/q | |||
| You also need a TRaX compliant processor(such as <a href="http://xml.apache.org/xalan-j">Xalan 2.x</a>) via JAXP 1.1</p> | |||
| <h3>Description</h3> | |||
| <p> | |||
| Invokes the Metamata Metrics / WebGain Quality Analyzer</a> source code | |||
| Invokes the Metamata Metrics / WebGain Quality Analyzer source code | |||
| analyzer on a set of Java files. | |||
| </p> | |||
| <p> | |||
| @@ -60,23 +60,23 @@ You also need a TRaX compliant processor(such as <a href="http://xml.apache.org/ | |||
| </tr> | |||
| </table> | |||
| <h3>Nested elements</h3> | |||
| For specifying the source code to analyze, you can either use a <tt>path</tt> or <tt>fileset</tt> elements (though a single path element is preferred, see note below).</i> | |||
| For specifying the source code to analyze, you can either use a <tt>path</tt> or <tt>fileset</tt> elements (though a single path element is preferred, see note below). | |||
| <h4>jvmarg</h4> | |||
| <p>Additional parameters may be passed to the VM via nested <code><jvmarg></code> | |||
| attributes. <code><jvmarg></code> allows all attributes described in <a href="index.html#arg">Command | |||
| attributes. <code><jvmarg></code> allows all attributes described in <a href="../using.html#arg">Command | |||
| line arguments</a>.</p> | |||
| <h4>classpath</h4> | |||
| <p>Sets class path (also source path unless one explicitly set). Overrides | |||
| METAPATH/CLASSPATH environment variables. The <tt>classpath</tt> element represents a <a href="index.html#path">PATH like | |||
| METAPATH/CLASSPATH environment variables. The <tt>classpath</tt> element represents a <a href="../using.html#path">PATH like | |||
| structure</a>.</p> | |||
| <h4>sourcepath</h4> | |||
| <p>Sets source path. Overrides the SOURCEPATH environment variable. The <tt>sourcepath</tt> element represents a <a href="index.html#path">PATH like | |||
| <p>Sets source path. Overrides the SOURCEPATH environment variable. The <tt>sourcepath</tt> element represents a <a href="../using.html#path">PATH like | |||
| structure</a>.</p> | |||
| <h4>path</h4> | |||
| <p>Sets the list of directories to analyze the code for metrics.;It represents a <a href="index.html#path">PATH structure</a>.</p> | |||
| <p>Sets the list of directories to analyze the code for metrics.;It represents a <a href="../using.html#path">PATH structure</a>.</p> | |||
| <h4>fileset</h4> | |||
| <p>Sets a set of files to analyze for metrics.source It represents a <a href="index.html#fileset">FILESET structure</a>.</p> | |||
| <p>Sets a set of files to analyze for metrics.source It represents a <a href="../CoreTypes/fileset.html">FILESET structure</a>.</p> | |||
| <p> | |||
| <font color="#FF0000"> | |||
| @@ -122,7 +122,5 @@ in the current directory), it can be run in Ant as follows: | |||
| <param value="&quot;'${report.dir}'&quot;"/> | |||
| </java> | |||
| </pre> | |||
| <hr> | |||
| </body> | |||
| </html> | |||
+ 5
- 6
docs/manual/OptionalTasks/mparse.html
View File
| @@ -91,14 +91,14 @@ | |||
| <h3>Nested elements</h3> | |||
| <h4>jvmarg</h4> | |||
| <p>Additional parameters may be passed to the VM via nested <code><jvmarg></code> | |||
| attributes. <code><jvmarg></code> allows all attributes described in <a href="index.html#arg">Command | |||
| attributes. <code><jvmarg></code> allows all attributes described in <a href="../using.html#arg">Command | |||
| line arguments</a>.</p> | |||
| <h4>classpath</h4> | |||
| <p>Sets class path (also source path unless one explicitly set). Overrides | |||
| METAPATH/CLASSPATH environment variables. The <tt>classpath</tt> element represents a <a href="index.html#path">PATH like | |||
| METAPATH/CLASSPATH environment variables. The <tt>classpath</tt> element represents a <a href="../using.html#path">PATH like | |||
| structure</a>.</p> | |||
| <h4>sourcepath</h4> | |||
| <p>Sets source path. Overrides the SOURCEPATH environment variable. The <tt>sourcepath</tt> element represents a <a href="index.html#path">PATH like | |||
| <p>Sets source path. Overrides the SOURCEPATH environment variable. The <tt>sourcepath</tt> element represents a <a href="../using.html#path">PATH like | |||
| structure</a>.</p> | |||
| <h3>Example</h3> | |||
| <pre> <mparse target="c:/metamata/examples/parseexamples/javagrammars/singlefile/JavaParser.jj" | |||
| @@ -112,6 +112,5 @@ structure</a>.</p> | |||
| example <tt>(JavaParser.jj)</tt> | |||
| and cleans up the intermediate Sun JavaCC file. | |||
| </p> | |||
| <hr> | |||
| </body> | |||
| </html> | |||
+ 2
- 2
docs/manual/OptionalTasks/native2ascii.html
View File
| @@ -19,7 +19,7 @@ | |||
| <em>includes</em> and <em>excludes</em> attributes. | |||
| For more information on file matching patterns, | |||
| see the section on | |||
| <a href="index.html../dirtasks.html#directorybasedtasks">directory based tasks</a>. | |||
| <a href="../dirtasks.html#directorybasedtasks">directory based tasks</a>. | |||
| If no <em>encoding</em> is specified, | |||
| the default encoding for the JVM is used. | |||
| If <em>ext</em> is specified, then output files are renamed | |||
| @@ -33,7 +33,7 @@ | |||
| </p> | |||
| <p> | |||
| This task forms an implicit <a href="index.html../CoreTypes/fileset.html">File Set</a>, | |||
| This task forms an implicit <a href="../CoreTypes/fileset.html">File Set</a>, | |||
| and supports all attributes of <code><fileset></code> | |||
| (<code>dir</code> becomes <code>src</code>) as well as | |||
| nested <code><include></code>, <code><exclude></code>, | |||
+ 67
- 81
docs/manual/OptionalTasks/pvcstask.html
View File
| @@ -23,19 +23,14 @@ Version 1.0 - 2001/01/31<br> | |||
| <hr> | |||
| <h2> | |||
| Table of Contents</h2> | |||
| <ul> | |||
| <li> | |||
| <a href="#introduction">Introduction</a></li> | |||
| <li> | |||
| <a href="#configuretask">Pvcs Task</a></li> | |||
| <br> | |||
| <li><a href="#introduction">Introduction</a></li> | |||
| <li><a href="#pvcs">Pvcs Task</a></li> | |||
| </ul> | |||
| <hr> | |||
| <h2> | |||
| <a NAME="introduction"></a>Introduction</h2> | |||
| The <pvcs> task allows the user of ant to extract the latest edition | |||
| <h2><a NAME="introduction">Introduction</a></h2> | |||
| 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 | |||
| developed by <a href="http://www.merant.com/products/pvcs">Merant</a>. | |||
| <br> | |||
| @@ -44,13 +39,10 @@ of PVCS (get and pcli) and must have access to the repository. Note that the way | |||
| the repository is platform dependent so use property to specify location of repository. | |||
| <br> | |||
| This version has been tested agains PVCS version 6.5 and 6.6 under Windows and Solaris. | |||
| <br> | |||
| <hr> | |||
| <h2> | |||
| <a NAME="pvcs"></a>Pvcs Task</h2> | |||
| <h3> | |||
| Description</h3> | |||
| <hr> | |||
| <h2><a NAME="pvcs">Pvcs Task</a></h2> | |||
| <h3>Description</h3> | |||
| The pvcs task is set to point at a PVCS repository and optionally a project | |||
| within that repository, and can from that specification get the latest | |||
| version of the files contained by the repository. | |||
| @@ -79,7 +71,7 @@ manuals)</td> | |||
| <td VALIGN=TOP WIDTH="12%">pvcsproject</td> | |||
| <td VALIGN=TOP WIDTH="78%">The project within the PVCS repository to extract | |||
| files from ("/" is root project and that is default if this attribute isn't | |||
| files from ("/" is root project and that is default if this attribute isn't | |||
| specified)</td> | |||
| <td VALIGN=TOP WIDTH="10%">No</td> | |||
| @@ -176,74 +168,68 @@ specified.</p> | |||
| </tr> | |||
| </table> | |||
| <h3> | |||
| Examples</h3> | |||
| The following set-up extracts the latest version of the files in the pvcs | |||
| repository. | |||
| <ul> <!-- =================================================================== | |||
| --> | |||
| <br> <!-- Get the latest version | |||
| --> | |||
| <br> <!-- =================================================================== | |||
| --> | |||
| <br> <target name="getlatest"> | |||
| <br> < pvcs repository="/mnt/pvcs" | |||
| pvcsproject="/myprj"/> | |||
| <br> </target></ul> | |||
| Now run: | |||
| <p> ant getlatest | |||
| <p>This will cause the following output to appear: | |||
| <pre> getlatest: | |||
| [pvcs] PVCS Version Manager (VMGUI) v6.6.10 (Build 870) for Windows NT/80x86 | |||
| [pvcs] Copyright 1985-2000 MERANT. All rights reserved. | |||
| [pvcs] PVCS Version Manager (get) v6.6.10 (Build 870) for Windows NT/80x86 | |||
| [pvcs] Copyright 1985-2000 MERANT. All rights reserved. | |||
| [pvcs] c:\myws\myprj\main.java <- C:\mypvcs\archives\myprj\main.java-arc | |||
| [pvcs] rev 1.1 | |||
| [pvcs] c:\myws\myprj\apache\tool.java <- C:\mypvcs\archives\myprj\apache\tools.java-arc | |||
| [pvcs] rev 1.5 | |||
| BUILD SUCCESSFUL | |||
| Total time: 19 seconds</pre> | |||
| <h3>Examples</h3> | |||
| The following set-up extracts the latest version of the files in the pvcs repository. | |||
| <pre> | |||
| <!-- =================================================================== --> | |||
| <!-- Get the latest version --> | |||
| <!-- =================================================================== --> | |||
| <target name="getlatest"> | |||
| <pvcs repository="/mnt/pvcs" pvcsproject="/myprj"/> | |||
| </target></ul> | |||
| </pre> | |||
| <p>Now run:</p> | |||
| <code>ant getlatest</code> | |||
| <p>This will cause the following output to appear:</p> | |||
| <pre> | |||
| getlatest: | |||
| [pvcs] PVCS Version Manager (VMGUI) v6.6.10 (Build 870) for Windows NT/80x86 | |||
| [pvcs] Copyright 1985-2000 MERANT. All rights reserved. | |||
| [pvcs] PVCS Version Manager (get) v6.6.10 (Build 870) for Windows NT/80x86 | |||
| [pvcs] Copyright 1985-2000 MERANT. All rights reserved. | |||
| [pvcs] c:\myws\myprj\main.java <- C:\mypvcs\archives\myprj\main.java-arc | |||
| [pvcs] rev 1.1 | |||
| [pvcs] c:\myws\myprj\apache\tool.java <- C:\mypvcs\archives\myprj\apache\tools.java-arc | |||
| [pvcs] rev 1.5 | |||
| BUILD SUCCESSFUL | |||
| Total time: 19 seconds</pre> | |||
| This next example extracts the latest version of the files in the pvcs | |||
| repository from two projects using nested <pvcsproject> elements. | |||
| <ul> <!-- =================================================================== | |||
| --> | |||
| <br> <!-- Get latest from myprj and myprj2 | |||
| --> | |||
| <br> <!-- =================================================================== | |||
| --> | |||
| <br> <target name="getlatest2"> | |||
| <br> <pvcs repository="/mnt/pvcs"> | |||
| <br> <pvcsproject name="/myprj" /> | |||
| <br> <pvcsproject name="/myprj2" /> | |||
| <br> </pvcs> | |||
| <br> </target></ul> | |||
| Now run: | |||
| <p> ant getlatest2 | |||
| <p>This will cause the following output to appear: | |||
| <pre> getlatest2: | |||
| [pvcs] PVCS Version Manager (VMGUI) v6.6.10 (Build 870) for Windows NT/80x86 | |||
| [pvcs] Copyright 1985-2000 MERANT. All rights reserved. | |||
| [pvcs] PVCS Version Manager (get) v6.6.10 (Build 870) for Windows NT/80x86 | |||
| [pvcs] Copyright 1985-2000 MERANT. All rights reserved. | |||
| [pvcs] c:\myws\myprj\main.java <- C:\mypvcs\archives\myprj\main.java-arc | |||
| [pvcs] rev 1.1 | |||
| [pvcs] c:\myws\myprj\apache\tool.java <- C:\mypvcs\archives\myprj\apache\tool.java-arc | |||
| [pvcs] rev 1.5 | |||
| [pvcs] c:\myws\myprj2\apache\tool2.java <- C:\mypvcs\archives\myprj2\apache\tool2.java-arc | |||
| [pvcs] rev 1.2 | |||
| BUILD SUCCESSFUL | |||
| Total time: 22 seconds</pre> | |||
| <pre> | |||
| <!-- ===================================================================--> | |||
| <!-- Get latest from myprj and myprj2 --> | |||
| <!-- ===================================================================--> | |||
| <target name="getlatest2"> | |||
| <pvcs repository="/mnt/pvcs"> | |||
| <pvcsproject name="/myprj"/> | |||
| <pvcsproject name="/myprj2"/> | |||
| </pvcs> | |||
| </target></ul> | |||
| </pre> | |||
| <hr WIDTH="100%"></ul> | |||
| <p>Now run:</p> | |||
| <code>ant getlatest2</code> | |||
| <p>This will cause the following output to appear:</p> | |||
| <pre> | |||
| getlatest2: | |||
| [pvcs] PVCS Version Manager (VMGUI) v6.6.10 (Build 870) for Windows NT/80x86 | |||
| [pvcs] Copyright 1985-2000 MERANT. All rights reserved. | |||
| [pvcs] PVCS Version Manager (get) v6.6.10 (Build 870) for Windows NT/80x86 | |||
| [pvcs] Copyright 1985-2000 MERANT. All rights reserved. | |||
| [pvcs] c:\myws\myprj\main.java <- C:\mypvcs\archives\myprj\main.java-arc | |||
| [pvcs] rev 1.1 | |||
| [pvcs] c:\myws\myprj\apache\tool.java <- C:\mypvcs\archives\myprj\apache\tool.java-arc | |||
| [pvcs] rev 1.5 | |||
| [pvcs] c:\myws\myprj2\apache\tool2.java <- C:\mypvcs\archives\myprj2\apache\tool2.java-arc | |||
| [pvcs] rev 1.2 | |||
| BUILD SUCCESSFUL | |||
| Total time: 22 seconds</pre> | |||
| <hr WIDTH="100%"> | |||
| PVCS is a registered trademark of MERANT. | |||
| </body> | |||
| </html> | |||
+ 2
- 3
docs/manual/OptionalTasks/starteam.html
View File
| @@ -14,14 +14,14 @@ Checks out files from a StarTeam project. | |||
| <p> | |||
| The <i>includes</i> and <i>excludes</i> attributes function differently from | |||
| other tasks in Ant. Multiple patters must be seperated by spaces, not | |||
| commas. See the examples for more information. | |||
| commas. See the examples for more information.</p> | |||
| <p> | |||
| This program makes use of functions from the StarTeam API. As a result | |||
| this task is only available to licensed users of StarTeam. You must have | |||
| <CODE>starteam-sdk.jar</CODE> in your classpath to run this task. | |||
| For more information about the StarTeam API and how to license it, see | |||
| the <a href="http://www.starbase.com">StarBase</a> web site. | |||
| the <a href="http://www.starbase.com">StarBase</a> web site.</p> | |||
| <h3>Parameters</h3> | |||
| <table border="1" cellpadding="2" cellspacing="0"> | |||
| @@ -149,7 +149,6 @@ This is an example of overlapping <i>includes</i> and <i>excludes</i> attributes | |||
| <i>excludes</i> takes precedence over <i>includes</i>, files named <code>index.html</code> will | |||
| not be checked out by this command. | |||
| <p> | |||
| <hr> | |||
| <p align="center"> | |||
| Copyright © 2000,2001 Apache Software Foundation. All rights Reserved. | |||
+ 7
- 11
docs/manual/OptionalTasks/wljspc.html
View File
| @@ -67,18 +67,14 @@ Example<br> | |||
| </wljspc><br> | |||
| </target> | |||
| </p> | |||
| <h3> | |||
| <br> | |||
| Limitations | |||
| </h3> | |||
| <p> | |||
| This works only on weblogic 4.5.1 | |||
| <br> | |||
| It compiles the files thru the Classic compiler only.<br> | |||
| Since it is my experience that weblogic jspc throws out of memory error on being given too<br> | |||
| many files at one go, it is called multiple times with one jsp file each. | |||
| <h3>Limitations</h3> | |||
| <ul> | |||
| <li>This works only on weblogic 4.5.1</li> | |||
| <li>It compiles the files thru the Classic compiler only.</li> | |||
| <li>Since it is my experience that weblogic jspc throws out of memory error on being given too | |||
| many files at one go, it is called multiple times with one jsp file each.</li> | |||
| </ul> | |||
| </body> | |||
| </html> | |||
+ 3
- 1
docs/manual/coretasklist.html
View File
| @@ -13,8 +13,10 @@ | |||
| <h3>Concepts and Types</h3> | |||
| <a href="dirtasks.html">Directory Based Tasks</a><br> | |||
| <a href="sysclasspath.html">build.sysclasspath</a><br> | |||
| <a href="CoreTypes/description.html">Description</a><br> | |||
| <a href="CoreTypes/patternset.html">Patternset</a><br> | |||
| <a href="CoreTypes/fileset.html">Fileset</a><br> | |||
| <a href="CoreTypes/filelist.html">FileList</a><br> | |||
| <a href="CoreTypes/fileset.html">FileSet</a><br> | |||
| <a href="CoreTypes/filterset.html">Filterset</a><br> | |||
| <a href="CoreTypes/mapper.html">File Mappers</a><br> | |||
| <a href="CoreTasks/common.html">Common Attributes</a><br> | |||
+ 2
- 2
docs/manual/dirtasks.html
View File
| @@ -126,7 +126,7 @@ way to select just the files you want.</p> | |||
| <h3>Examples</h3> | |||
| <pre> | |||
| <copy todir="${dist}"> | |||
| <copy todir="${dist}"> | |||
| <fileset dir="${src}" | |||
| includes="**/images/*" | |||
| excludes="**/*.gif" | |||
| @@ -138,7 +138,7 @@ destination directory defined by <code>${dist}</code>, | |||
| but excludes all <code>*.gif</code> files from the copy.</p> | |||
| <p> This example can also be expressed using nested elements:</p> | |||
| <pre> | |||
| <copy todir="${dist}"> | |||
| <copy todir="${dist}"> | |||
| <fileset dir="${src}"> | |||
| <include name="**/images/*"/> | |||
| <exclude name="**/*.gif"/> | |||
+ 3
- 3
docs/manual/install.html
View File
| @@ -68,7 +68,7 @@ required to run Ant. | |||
| To install Ant, choose a directory and copy the distribution | |||
| file there. This directory will be known as ANT_HOME. | |||
| <br> | |||
| </p> | |||
| <table width="80%"> | |||
| <tr> | |||
| @@ -87,8 +87,8 @@ installed in a <b>short</b> path, such as C:\Ant.</i> | |||
| </td> | |||
| </tr> | |||
| </table> | |||
| <br> | |||
| <p> | |||
| Before you can run ant there is some additional set up you | |||
| will need to do:</p> | |||
| <ul> | |||
| @@ -201,7 +201,7 @@ used for the remainder of the build steps. </li> | |||
| <li>Invokes the bootstrapped Ant with the parameters passed to the build script. In | |||
| this case, these parameters define an Ant property value and specify the "dist" target | |||
| in Ant's own <code>build.xml</code> file. | |||
| in Ant's own <code>build.xml</code> file.</li> | |||
| </ul> | |||
| <p>On most occasions you will not need to explicitly bootstrap Ant since the build | |||
+ 3
- 3
docs/manual/using.html
View File
| @@ -136,9 +136,8 @@ have the name "init".</p> | |||
| </tr> | |||
| </table> | |||
| <a name="tasks"> | |||
| <h3>Tasks</h3> | |||
| </a> | |||
| <h3><a name="tasks">Tasks</a></h3> | |||
| <p>A task is a piece of code that can be executed.</p> | |||
| <p>A task can have multiple attributes (or arguments, if you prefer). The value | |||
| of an attribute might contain references to a property. These references will be | |||
| @@ -207,6 +206,7 @@ For example, <code>${os.name}</code> expands to the | |||
| name of the operating system.</p> | |||
| <p>For a list of system properties see | |||
| <a href="http://java.sun.com/j2se/1.3/docs/api/java/lang/System.html#getProperties()">the Javadoc of System.getProperties</a>. | |||
| </p> | |||
| <p>In addition, Ant has some built-in properties:</p> | |||
| <pre> | |||
| basedir the absolute path of the project's basedir (as set | |||