A recorder is a listener to the current build process that records the
-output to a file.
+output to a file.
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).
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.
@@ -66,7 +66,7 @@ a buildFinished event.
Examples
The following build.xml snippet is an example of how to use the recorder
-to record just the <javac> task:
+to record just the <javac> task:
...
<compile >
@@ -80,7 +80,7 @@ to record just the <javac> task:
The following two calls to <record> set up two
recorders: one to file "records-simple.log" at logging level info
(the default) and one to file "ISO.log" using logging level of
-verbose.
+verbose.
...
<record name="records-simple.log" />
@@ -90,7 +90,7 @@ recorders: one to file "records-simple.log" at logging level inf
Notes
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:
| Attribute |
diff --git a/docs/manual/CoreTasks/sequential.html b/docs/manual/CoreTasks/sequential.html
index 38603c9f0..62bae9c7e 100644
--- a/docs/manual/CoreTasks/sequential.html
+++ b/docs/manual/CoreTasks/sequential.html
@@ -30,7 +30,7 @@ sequential task.
</parallel>
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.
Copyright © 2000,2001 Apache Software Foundation. All rights
diff --git a/docs/manual/CoreTasks/tar.html b/docs/manual/CoreTasks/tar.html
index 86d1f21ac..d237625df 100644
--- a/docs/manual/CoreTasks/tar.html
+++ b/docs/manual/CoreTasks/tar.html
@@ -66,7 +66,7 @@ the limit.
Determines how long files (>100 chars) are to be
handled. Allowable values are "truncate", "fail",
"warn", "omil" and "gnu". Default is
- "warn".
+ "warn". |
No |
diff --git a/docs/manual/CoreTasks/tstamp.html b/docs/manual/CoreTasks/tstamp.html
index 894d98596..81dd19a41 100644
--- a/docs/manual/CoreTasks/tstamp.html
+++ b/docs/manual/CoreTasks/tstamp.html
@@ -14,12 +14,12 @@
properties in the current project. The DSTAMP property is in the
format "yyyymmdd", TSTAMP is in the
format "hhmm", and TODAY is in the
-format "month day year".
+format "month day year".
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.
Parameters
@@ -108,7 +108,7 @@ and TODAY properties according to the default formats.
sets the standard properties as well as the property
TODAY_UK with the date/time pattern "d-MMMM-yyyy"
-using English locale (eg. 21-May-2001).
+using English locale (eg. 21-May-2001).
<tstamp>
diff --git a/docs/manual/CoreTasks/zip.html b/docs/manual/CoreTasks/zip.html
index 315c8624a..f9f7092c4 100644
--- a/docs/manual/CoreTasks/zip.html
+++ b/docs/manual/CoreTasks/zip.html
@@ -37,7 +37,7 @@ only reflect the relative paths of files within each fileset. The Zip tas
ZIP file already exists. When set to yes, the ZIP file is
updated with the files specified. (New files are added; old files are
replaced with the new versions.) When set to no (the
-default) the ZIP file is overwritten.
+default) the ZIP file is overwritten.
The whenempty parameter controls what happens when no files match.
If skip (the default), the ZIP is not created and a warning is issued.
If fail, the ZIP is not created and the build is halted with an error.
diff --git a/docs/manual/Integration/Antidote.html b/docs/manual/Integration/Antidote.html
index cce925978..e4cadd215 100644
--- a/docs/manual/Integration/Antidote.html
+++ b/docs/manual/Integration/Antidote.html
@@ -31,7 +31,7 @@
Status
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:
- Reading Ant build files.
- Selecting targets and executing them.
@@ -39,9 +39,8 @@
- Modification of (some) build file components.
- Saving modified build file.
-
- Current development tasks include:
+
Current development tasks include:
- A more complete set of target and task editing
capabilities.
@@ -49,7 +48,6 @@
existing code bases.
- Better build progress monitoring.
-
The Antidote source distribution comes with requirements and
design documentation that better cover the details of application
@@ -62,7 +60,7 @@
The source code for Antidote is located in a separate Module
(jakarta-ant-antidote) in CVS.
All the existing documentation can
- be found there where new contributors should read:
+ be found there where new contributors should read:
- Design Overview
- Feature List
@@ -75,11 +73,11 @@
HREF="http://jakarta.apache.org/site/mail.html">jakarta-ant
mailing list. The application infrastructure is fairly
complete, but there are almost unlimited opportunities for feature
- contributions.
+ contributions.
Aspiring contributors new to the Jakarta Project should
(carefully) read the following for details on the contribution
- process:
+ process:
- Get
diff --git a/docs/manual/Integration/VAJAntTool.html b/docs/manual/Integration/VAJAntTool.html
index 174eee8d6..18e26e35c 100644
--- a/docs/manual/Integration/VAJAntTool.html
+++ b/docs/manual/Integration/VAJAntTool.html
@@ -166,7 +166,7 @@ FileSets.
| defaultexcludes |
- use default excludes when exporting (default: "yes")
+ | use default excludes when exporting (default: "yes") |
no |
@@ -561,7 +561,7 @@ Project name at the beginning of the "includes" parameter.
Q: When I import Ant into my Workspace, I get Problems reported. Can I
ignore them?
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:
- Classes from javax.xml.parser missing - install a compatible parser
(see installation)
@@ -570,7 +570,6 @@ Problems you can't ignore:
Utility feature (see installation).
-
Q: Why is the task name vajload when the class is called VAJLoadProjects?
A: At the moment this task can load only project versions. This is reflected
diff --git a/docs/manual/OptionalTasks/BorlandEJBTasks.html b/docs/manual/OptionalTasks/BorlandEJBTasks.html
index c4723e2cc..8759b5197 100644
--- a/docs/manual/OptionalTasks/BorlandEJBTasks.html
+++ b/docs/manual/OptionalTasks/BorlandEJBTasks.html
@@ -9,11 +9,11 @@
Description
-The BorlandDeployTool is a vendor specific nested element for the Ejbjar optional task.
+
The BorlandDeployTool is a vendor specific nested element for the Ejbjar optional task.
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.
Borland element
@@ -76,7 +76,7 @@
Examples
The following build.xml snippet is an example of how to use Borland element
- into the ejbjar task
+ into the ejbjar task
<ejbjar srcdir="${build.classes}" basejarname="vsmp" descriptordir="${rsc.dir}/hrmanager">
<borland destdir="lib" verify="on" generateclient="on">
<classpath refid="classpath" />
diff --git a/docs/manual/OptionalTasks/BorlandGenerateClient.html b/docs/manual/OptionalTasks/BorlandGenerateClient.html
index 82159d729..2a0c9f3a1 100644
--- a/docs/manual/OptionalTasks/BorlandGenerateClient.html
+++ b/docs/manual/OptionalTasks/BorlandGenerateClient.html
@@ -11,7 +11,7 @@
Description
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.
Parameters
@@ -47,7 +47,7 @@
Examples
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.
<blgenclient ejbjar="lib/secutest-ejb.jar" clientjar="lib/client.jar" debug="true" mode="java">
<classpath>
diff --git a/docs/manual/OptionalTasks/dotnet.html b/docs/manual/OptionalTasks/dotnet.html
index 2d710e6a7..727afa228 100644
--- a/docs/manual/OptionalTasks/dotnet.html
+++ b/docs/manual/OptionalTasks/dotnet.html
@@ -120,9 +120,9 @@ version crimson.jar and jaxp.jar.
This is the beta-2 revision of the tasks.
- ILASM: pulled the owner attribute, added keyfile for giving binaries a strong name
-(MD5 hash of the checksum)
-
- CSC: added win32res , noConfig, utf8output, fullpaths
-
- CSC:
+(MD5 hash of the checksum)
+- CSC: added win32res , noConfig, utf8output, fullpaths
+- CSC:
Version 0.3
diff --git a/docs/manual/OptionalTasks/ejb.html b/docs/manual/OptionalTasks/ejb.html
index 736c8e6ee..5325cb65c 100644
--- a/docs/manual/OptionalTasks/ejb.html
+++ b/docs/manual/OptionalTasks/ejb.html
@@ -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.
Parameters:
@@ -222,7 +222,7 @@ Parameters:
| iasdescriptor |
-iAS-specific EJB XML descriptor (typically titled "ias-ejb-jar.xml). |
+iAS-specific EJB XML descriptor (typically titled "ias-ejb-jar.xml"). |
Yes |
@@ -529,7 +529,7 @@ include:
- Borland Application Server 4.5
- iPlanet Application Server 6.0
- Jboss 2.1 and above
- - Weblogic 5.1/6.0 session/entity beans using the weblogic.ejbc tool
+
- Weblogic 5.1/6.0 session/entity beans using the weblogic.ejbc tool
- TOPLink for WebLogic 2.5.1-enabled entity beans
@@ -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.
-
-Jboss element
-
+
+
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.
-
-Weblogic element
-
+
+
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'.
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
<ejbjar descriptordir="${dd.dir}" srcdir="${build.classes.server}">
@@ -1067,9 +1065,8 @@ This will create only one TOPLink-enabled ejb jar file - 'Address.jar'.
</ejbjar>
-
-iPlanet Application Server (iAS) element
-
+
+
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.
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.
Parameters:
@@ -1166,7 +1163,7 @@ If omitted, it defaults to ".jar".
As noted above, the iplanet element supports additional <classpath>
-nested elements.
+nested elements.
Examples
This example demonstrates the typical use of the <iplanet> nested element.
diff --git a/docs/manual/OptionalTasks/icontract.html b/docs/manual/OptionalTasks/icontract.html
index f57fe52de..a8fe2319a 100644
--- a/docs/manual/OptionalTasks/icontract.html
+++ b/docs/manual/OptionalTasks/icontract.html
@@ -44,7 +44,6 @@ Instruments Java classes with i
builddir |
Indicates where the compiled instrumented classes should go.
Defaults to the value of instrumentdir.
-
NOTE: 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). |
diff --git a/docs/manual/OptionalTasks/jdepend.html b/docs/manual/OptionalTasks/jdepend.html
index a8b190256..5bbe5c75e 100644
--- a/docs/manual/OptionalTasks/jdepend.html
+++ b/docs/manual/OptionalTasks/jdepend.html
@@ -15,9 +15,9 @@
Invokes the JDepend parser.
-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."
+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."
Source file directories are defined by nested <sourcespath>, see nested elements.
@@ -27,8 +27,6 @@ effectively manage and control package dependencies."
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.
-
-
Parameters
diff --git a/docs/manual/OptionalTasks/jjtree.html b/docs/manual/OptionalTasks/jjtree.html
index 4e76e9c8d..6a72bb866 100644
--- a/docs/manual/OptionalTasks/jjtree.html
+++ b/docs/manual/OptionalTasks/jjtree.html
@@ -23,11 +23,11 @@ so that ant can find the JavaCC classes. Optionally, you can also set the
outputdirectory
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.
This task only invokes JJTree if the grammar file is newer than the
-generated JavaCC file.
-
-Parameters
+generated JavaCC file.
+
+Parameters
diff --git a/docs/manual/OptionalTasks/jpcoverage.html b/docs/manual/OptionalTasks/jpcoverage.html
index 5b8709e24..4bf18fe00 100644
--- a/docs/manual/OptionalTasks/jpcoverage.html
+++ b/docs/manual/OptionalTasks/jpcoverage.html
@@ -24,7 +24,6 @@ and is not intended as a replacement to the manual.
Tasks
-
| JPCoverage |
@@ -39,7 +38,6 @@ and is not intended as a replacement to the manual.
Create a report from a snapshot |
-
@@ -97,8 +95,8 @@ Perform code covering functions by comparing source code line execution to the p
| exitprompt |
- Toggles display of the console prompt: "Press Enter to close
- this window." "always": Always displays the prompt. "never": Never displays the
+ | 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. |
No, default is "never" |
@@ -150,7 +148,7 @@ Perform code covering functions by comparing source code line execution to the p
classpath
jpcoverage supports a nested <classpath>
-element, that represents a PATH like
+element, that represents a PATH like
structure.
jvmarg
@@ -169,13 +167,13 @@ attributes, for example:
would run the coverage on "MyClass" in classic mode VM.
<jvmarg> allows all attributes described in Command line arguments.
+href="../using.html#arg">Command line arguments.
arg
Parameters may be passed to the executed class via nested <arg>
-attributes, as described in Command line arguments.
+attributes, as described in Command line arguments.
socket
@@ -204,7 +202,7 @@ attributes, as described in Command line arguments.
filters
Defines class/method filters based on pattern matching.
-The syntax is filters is similar to a fileset.
+The syntax is filters is similar to a fileset.
@@ -348,7 +346,7 @@ same class.
-jpcovmerge collects snapshots using the nested <FileSet>
+jpcovmerge collects snapshots using the nested <FileSet>
element.
@@ -368,7 +366,7 @@ directory snapshots. The resulting file will be named merge.jpc
-JPCovReport
+
Description
@@ -425,7 +423,7 @@ Oro in Ant classpath, to run the reference feature.
sourcepath
-Path to source files can be set via nested sourcepath elements that are PATH like structures.
+Path to source files can be set via nested sourcepath elements that are PATH like structures.
reference (only applies to format="xml")
@@ -456,7 +454,7 @@ the XML report accordingly. In short, it will:
-Path to the reference set of files can be set via nested classpath elements that are PATH like structures.
+Path to the reference set of files can be set via nested classpath elements that are PATH like structures.
filters
diff --git a/docs/manual/OptionalTasks/junit.html b/docs/manual/OptionalTasks/junit.html
index 97e3e1496..da49c2f80 100644
--- a/docs/manual/OptionalTasks/junit.html
+++ b/docs/manual/OptionalTasks/junit.html
@@ -97,7 +97,7 @@ structure.
jvmarg
If fork is enabled, additional parameters may be passed to the new
-VM via nested <jvmarg> attributes, for example:
+VM via nested <jvmarg> attributes, for example:
<junit fork="yes">
@@ -106,7 +106,7 @@ VM via nested <jvmarg> attributes, for example:
</junit>
-would run the test in a VM without JIT.
+would run the test in a VM without JIT.
<jvmarg> allows all attributes described in Command line arguments.
@@ -116,7 +116,7 @@ href="../using.html#arg">Command line arguments.
Use nested <sysproperty> 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 environment variables.
+The attributes for this element are the same as for environment variables.
<junit fork="no">
@@ -125,7 +125,7 @@ The attributes for this element are the same as for
-Runs the test defined in my.test.TestCase in the same
+Runs the test defined in my.test.TestCase in the same
VM. No output will be generated unless the test fails.
-
+
<junit printsummary="yes" fork="yes" haltonfailure="yes">
<formatter type="plain" />
<test name="my.test.TestCase" />
</junit>
-Runs the test defined in my.test.TestCase in a
+Runs the test defined in my.test.TestCase 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
TEST-my.test.TestCase.txt. The build process will be
stopped if the test fails.
-
+
<junit printsummary="yes" haltonfailure="yes">
<classpath>
<pathelement location="${build.tests}" />
@@ -361,7 +361,7 @@ stopped if the test fails.
</junit>
-Runs my.test.TestCase in the same VM (ignoring the
+Runs my.test.TestCase 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 result.xml.
diff --git a/docs/manual/OptionalTasks/junitreport.html b/docs/manual/OptionalTasks/junitreport.html
index fa2f3642e..71cbfde14 100644
--- a/docs/manual/OptionalTasks/junitreport.html
+++ b/docs/manual/OptionalTasks/junitreport.html
@@ -11,13 +11,13 @@ a stylesheet on the resulting merged document to provide a browsable report of
the testcases results.
Requirements
The task will run with either Xalan 2.x
-or Xalan 1.2.2.
+or Xalan 1.2.2.
Note: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.
-
+
Parameters