DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10403>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10403
The way in which property values are used can at times be very unintuitive
Summary: The way in which property values are used can at times
be very unintuitive
Product: Ant
Version: unspecified
Platform: Other
OS/Version: Other
Status: NEW
Severity: Enhancement
Priority: Other
Component: Core tasks
AssignedTo: ant-dev@jakarta.apache.org
ReportedBy: wtff@freenet.de
I would like to do a very simple thing:
Test network conditions (socket, http) and generate a report that tells me if
every network resource is up or not.
I found that doing this can be very complicated because of some interrelating
issues.
- property values can be true, false or NOT SET, also a property can be set
only once and is then like a constant.
- the waitfor/condition tasks set a property to true or leave it unset.
Now, if I wanted to test whether a socket is active and report this, I would
like to do it like this:
<target name="socketcheck" depends="">
<condition property="socket.server1.3302">
<socket server="1.1.1.1" port="3302"/>
</condition>
</target>
<target name="all" depends="socketcheck">
<echo>
Port 3302 on Server 1 available : ${socket.server1.3302}
</echo>
</target>
However, the first issue is that within the <condition> task, it is
no˙ |