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. 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 && operator in some programming languages, 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. 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 || operator in some programming languages, as soon as one of the nested conditions is true, no other condition will be evaluated.

The <xor> element performs an exclusive or on all nested elements, similar to the ^ operator in PHP. It only evaluates to true if an odd number of nested conditions are true. There is no shortcutting of evaluation, unlike the <and> and <or> tests. It doesn't have any attributes and accepts all nested elements of the condition task as nested elements as well.

Test whether the current operating system is of a given type.

Supported values for the family attribute are:

Note: machines running OSX match on the mac and unix families! To test for Macs that don't run a Unix-like OS, use the following code:

<condition property="isMacOsButNotMacOsX">
    <and>
        <os family="mac"/>
        <not>
            <os family="unix"/>
        </not>
    </and>
</condition>

Tests whether the two given Strings are identical

Compares two given versions

<versioncompare version="${aProperty}" desiredVersion="1.3" operator="gt" />

This condition internally uses PHP version_compare(). Operators and behavior are the same.

Condition to wait for a HTTP request to succeed.

Attributes are:

<http url="http://url.to.test" errorsBeginAt="404" />

PDOSQLExecTask can also be used as condition. Returns true when the connection to a database succeeds, and false otherwise. This condition requires the PDO extension to work properly.

This is a typical use case for PDOSQLExec condition:

<target name="wait-for-mysql">
    <waitfor timeoutproperty="mysql.timeout" maxwait="60" maxwaitunit="second">
        <pdosqlexec url="mysql:host=localhost;port=3306"
                  userid="${db.username}"
                  password="${db.password}"/>
    </waitfor>
    <fail if="mysql.timeout">Cannot reach database</fail>
</target>

If you also want to check if a specific schema exists, you can include the schema's name in your url:

<pdosqlexec url="mysql:host=127.0.0.1;port=3306;dbname=foo"
          userid="${db.username}"
          password="${db.password}"/>

This condition uses PDO behind the scenes. Therefore, if you have installed the appropriate driver you should also be able to reach many other DBMS. For example, for a PostgreSQL database:

<pdosqlexec url="pgsql:host=localhost;port=5432;dbname=bar"
          userid="${db.username}"
          password="${db.password}"/>

You should never hard-code sensitive data in your buildfile, you could use an unversioned property file instead. Also, be careful when using verbose or debug mode since you can expose sensitive data.

Condition to test for a (tcp) listener on a specified host and port.

<socket server="localhost" port="80" />

Condition returns true if selected partition has the requested space, false otherwise.

On Unix-like platforms:

<hasfreespace partition="/" needed="250M" />

On Windows:

<hasfreespace partition="c:" needed="10M" />

This condition internally uses PHP disk_free_space().

Test whether a given property has been set in this project.

Tests whether a string contains another one.

Tests whether a string evaluates to true.

<istrue value="${someproperty}"/>
<istrue value="false"/>

Tests whether a string evaluates to not true, the negation of <istrue>

<isfalse value="${someproperty}"/>
<isfalse value="false"/>

Tests whether a property evaluates to true.

<ispropertytrue property="someproperty"/>

Tests whether a property evaluates to not true, the negation of <ispropertytrue>

<ispropertyfalse property="someproperty"/>

Tests whether a specified reference exists.

<referenceexists ref="${someid}"/>

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.

<if>
    <available file="README.md"/>
    <then>
        <echo message="Please read README.md"/>
    </then>
</if>

Test two files for matching. Nonexistence of one file results in "false", although if neither exists they are considered equal in terms of content. This test does a byte for byte comparison, so test time scales with byte size. NB: if the files are different sizes, one of them is missing or the filenames match the answer is so obvious the detailed test is omitted.

<filesmatch file1="${file1}" file2="${file2}"/>

Test whether a file passes an embedded selector.

<isfileselected file="a.xml">
  <date datetime="06/28/2000 2:02 pm" when="equal"/>
</isfileselected>

Test the return code of an executable for failure.

<exec command="test" returnProperty="return.code"/>
<if>
    <isfailure code="${return.code}"/>
    <then><echo msg="${return.code}"/></then>
</if>

Test if the specified string matches the specified regular expression pattern.