diff --git a/WHATSNEW b/WHATSNEW
index 2679454c6..12c69046a 100644
--- a/WHATSNEW
+++ b/WHATSNEW
@@ -63,7 +63,7 @@ Other changes:
* Added support for specifying CVS_RSH in the
All conditions to test are specified as nested elements.
- -The <not>
element expects exactly one other
-condition to be nested into this element, negating the result of the
-condition. It doesn't have any attributes and accepts all nested
-elements of the condition task as nested elements as well.
-The <and>
element doesn't have any attributes and
-accepts an arbitrary number of conditions as nested elements - all
-nested elements of the condition task are supported. This condition
-is true if all of its contained conditions are, conditions will be
-evaluated in the order they have been specified in the build file.
The <and>
condition has the same shortcut
-semantics as the Java && operator, as soon as one of the
-nested conditions is false, no other condition will be evaluated.
-The <or>
element doesn't have any attributes and
-accepts an arbitrary number of conditions as nested elements - all
-nested elements of the condition task are supported. This condition
-is true if at least one of its contained conditions is, conditions
-will be evaluated in the order they have been specified in the build
-file.
The <or>
condition has the same
-shortcut semantics as the Java || operator, as soon as one of the
-nested conditions is true, no other condition will be evaluated.
This condition is identical to the Available task, all attributes and nested -elements of that task are supported, the property and value attributes -are redundant and will be ignored.
- -This condition is identical to the Uptodate task, all attributes and nested -elements of that task are supported, the property and value attributes -are redundant and will be ignored.
- -Test whether the current operating system is of a given type. Each -defined attribute is tested and the result is true only if all -the tests succeed. -
-Attribute | -Description | -Required | -
family | -The name of the operating system family to expect. | -No | -
name | -The name of the operating system to expect. | -No | -
arch | -The architecture of the operating system to expect. | -No | -
version | -The version of the operating system to expect. | -No | -
Supported values for the family attribute are: -
Tests whether the two given Strings are identical
-Attribute | -Description | -Required | -
arg1 | -First string to test. | -Yes | -
arg2 | -Second string to test. | -Yes | -
Test whether a given property has been set in this project.
-Attribute | -Description | -Required | -
property | -The name of the property to test. | -Yes | -
This condition is identical to the Checksum task, all attributes and nested -elements of that task are supported, the property and overwrite -attributes are redundant and will be ignored.
+All conditions to test are specified as nested elements, for a +complete list see here.
diff --git a/docs/manual/CoreTasks/conditions.html b/docs/manual/CoreTasks/conditions.html new file mode 100644 index 000000000..9c46488b3 --- /dev/null +++ b/docs/manual/CoreTasks/conditions.html @@ -0,0 +1,181 @@ + + + + +Apache Ant User Manual + + + + +Conditions
+ +These are the nested elements that can be used as conditions in the +
+ +<condition>
and +<waitfor>
tasks.not
+The
+ +<not>
element expects exactly one other +condition to be nested into this element, negating the result of the +condition. It doesn't have any attributes and accepts all nested +elements of the condition task as nested elements as well.and
+The
+<and>
element doesn't have any attributes and +accepts an arbitrary number of conditions as nested elements - all +nested elements of the condition task are supported. This condition +is true if all of its contained conditions are, conditions will be +evaluated in the order they have been specified in the build file.The
+ +<and>
condition has the same shortcut +semantics as the Java && operator, as soon as one of the +nested conditions is false, no other condition will be evaluated.or
+The
<or>
element doesn't have any attributes and +accepts an arbitrary number of conditions as nested elements - all +nested elements of the condition task are supported. This condition +is true if at least one of its contained conditions is, conditions +will be evaluated in the order they have been specified in the build +file.The
+ +<or>
condition has the same +shortcut semantics as the Java || operator, as soon as one of the +nested conditions is true, no other condition will be evaluated.available
+This condition is identical to the Available task, all attributes and nested +elements of that task are supported, the property and value attributes +are redundant and will be ignored.
+ +uptodate
+This condition is identical to the Uptodate task, all attributes and nested +elements of that task are supported, the property and value attributes +are redundant and will be ignored.
+ +os
+Test whether the current operating system is of a given type. Each +defined attribute is tested and the result is true only if all +the tests succeed. +
+
Attribute | +Description | +Required | +
family | +The name of the operating system family to expect. | +No | +
name | +The name of the operating system to expect. | +No | +
arch | +The architecture of the operating system to expect. | +No | +
version | +The version of the operating system to expect. | +No | +
Supported values for the family attribute are: +
Tests whether the two given Strings are identical
+Attribute | +Description | +Required | +
arg1 | +First string to test. | +Yes | +
arg2 | +Second string to test. | +Yes | +
Test whether a given property has been set in this project.
+Attribute | +Description | +Required | +
property | +The name of the property to test. | +Yes | +
This condition is identical to the Checksum +task, all attributes and nested elements of that task are supported, +the property and overwrite attributes are redundant and will be +ignored.
+ +The http
condition checks for a valid response from a
+web server of the specified url.
Attribute | +Description | +Required | +
url | +The full URL of the page to request. The web server must + return a status code of <500.. | +Yes. | +
The socket
condition checks for the existence of a
+TCP/IP listener at the specified host and port.
Attribute | +Description | +Required | +
server | +The DNS name or IP address of the server. | +Yes. | +
port | +The port number to connect to. | +Yes. | +
Copyright © 2001 Apache Software +Foundation. All rights Reserved.
+ + + \ No newline at end of file diff --git a/docs/manual/CoreTasks/waitfor.html b/docs/manual/CoreTasks/waitfor.html new file mode 100644 index 000000000..0b42d8767 --- /dev/null +++ b/docs/manual/CoreTasks/waitfor.html @@ -0,0 +1,79 @@ + + + + +Blocks execution until a set of specified conditions become true. This is intended + to be used with the parallel task to + synchronize a set of processes.
+The conditions to wait for are defined in nested elements, if multiple conditions + are specified, then the task will wait until all conditions are true..
+ +The time attributes (maxwait and checkevery) are specified in milliseconds + unless the values are followed by one of the following suffixes: "ms", + "s", "m", "h" which cause the value to be interpreted + as milliseconds, seconds, minutes or hours.
+Attribute | +Description | +Required | +
maxwait | +The maximum amount of time to wait for all the required conditions + to become true before failing the task. Defaults to 5 minutes. | +No | +
checkevery | +The amount of time to wait between each test of the conditions. + Defaults to 200mS. | +No | +
The available conditions that satisfy the
+<waitfor>
task are the same as those for the
+<condition>
task. See
+here for the full list.
+++
<waitfor maxwait="30s">
+ <available file="errors.log"/>
+ </waitfor>
waits up to 30 seconds for a file called errors.log to appear.
++++
<waitfor maxwait="3m" checkevery="500ms">
+ <http url="http://localhost/myapp/index.html"/>
+ </waitfor>
waits up to 3 minutes (and checks every 500mS) for a web server on localhost + to serve up the specified URL.
++++
<waitfor maxwait="10s">
+ <and>
+ <socket server="dbserver" port="1521"/>
+ <http url="http://webserver/mypage.html"/>
+ </and>
+ </waitfor>
waits up to 10 seconds for a server on the dbserver machine to begin listening + on port 1521 and for the http://webserver/mypage.html web page + to become available.
+Copyright © 2000,2001 Apache Software Foundation. All rights +Reserved.
+ + + + diff --git a/docs/manual/coretasklist.html b/docs/manual/coretasklist.html index 31e4e5be2..666094c81 100644 --- a/docs/manual/coretasklist.html +++ b/docs/manual/coretasklist.html @@ -81,6 +81,8 @@ Unwar