ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 10401] - waitfor task doesn't shut off socket conditions in every case
Date Fri, 12 Jul 2002 19:48:34 GMT
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=10401>.
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=10401

waitfor task doesn't shut off socket conditions in every case





------- Additional Comments From stevel@apache.org  2002-07-12 19:48 -------
>- The Socket class also has a method called setSO_Timeout() and in version 1.4 
>there is also a constructor taking a timeout value as an argument.

I dont think setSO_Timeout has any effect on connect timeouts; it is there for
blocking reads. Didnt know about the java1.4 enhancement to connect(), but it
would only be relevent to java1.4.

If you want to make a change to the <socket> and <http> tests to take a timeout
inside that then uses reflection to call the java1.4 binding, and add a Junit
test case to verify that it works, then it can go in. An evenings work, by my
estimate. 

regarding your comments on condition; I see you still dont fully know how to use
properties in Ant, as per other open bugs. Once you understand, it all makes
sense. Note that if= and unless= in targets go by set/unset, not true and false,
so an unset condition wont execute an if= guarded target.

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message