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-11 19:14 ------- >What I try to do is to have some property that is set to "true" if a network >connection is up and to "false" otherwise. <condition> doesnt set a property if the condition is false; do the condition first, the other set *after* immutablitity was settled on because it lets outside agencies -the user, continuous integration tools like Gump, other build files, control your build file from the outside by setting properties. eg. on the command line you could go ant -Dsocket.server1.3302=false have the condition be the following (the or shortcuts so if the property is set to true or false, the test is skipped) <condition property="socket.server1.3302"> <or> <isset property="socket.server1.3302"/> <socket server="1.1.1.1" port="3302"/> </or> </condition> <property name="socket.mscdev1.3301" value="false"/> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
