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=25258>. 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=25258 System.in closed by <java> [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2003-12-07 22:26 ------- I believe the 1.6 behaviour is correct and 1.5 was incorrect. When you use <java> without any form of input and the program tries to read from System.in, it *should* get -1 (i.e. EOF) since there is no input available. Blocking is not a good behaviour here since it tends to hang the build. If the process eats the CPU, I would suspect that the java program is not handling EOF situations correctly. When you say "with Ant 1.5.4 the read() method blocks as expected", I have to say, this is not "expected" but was a bug in Ant prior top Ant 1.6 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
