You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2003/12/07 23:26:15 UTC
DO NOT REPLY [Bug 25258] -
System.in closed by
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>
conor@cortexebusiness.com.au changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From conor@cortexebusiness.com.au 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: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org