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=10404>. 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=10404 The way in which property values are used can at times be very unintuitive ------- Additional Comments From [EMAIL PROTECTED] 2002-07-02 12:47 ------- sorry, hit the commit button too early ;) ... write s.th like this, which looks very overloaded and inverted too: <target name="socketcheck" depends=""> <waitfor timeoutproperty="socket.server1.3301" maxwait="5" maxwaitunit="second"> <not> <socket server="1.1.1.1" port="3301"/> </not> </waitfor> <condition property="socket.mscdev1.3301" value="false"> <not> <isset property="socket.mscdev1.3301" /> </not> </condition> </target> <target name="all" depends="socketcheck"> <echo> Port 3301 on server 1 available : ${socket.server1.3301} </echo> </target> You see that this is a little bit crooked. Now assume that I would like to test a whole bunch of socket connections. In addition, the waitfor/socket task doesn't seem to work properly in terms of the timeout constraints, because if the ip address tested is not available, the tasks waits very long, but i posted this within a separate report. I'd propose to merge the waitfor and condition task into one single task and name it condition. (bug-report 10398) Then I would either make this task set a property in any case, to true/false by default or two two other values that might be specified within attributes of the new condition task. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
