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 5003] - exec task does not return after executed command finished on Windows only
Date Mon, 03 Dec 2001 20:05:05 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=5003>.
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=5003

exec task does not return after executed command finished on Windows only





------- Additional Comments From steve_l@iseran.com  2001-12-03 12:05 -------
This is an interesting problem, and not one I have seen myself, despite my 
extensive use of ant on NT. I wonder if it is showing some interesting side 
effects of the call to exec() inside the sub process.

Whatever, your supplied path [NB, please use diff -u in future] would seem to 
ensure ant continues, and given that the stop() method is called after the 
process has terminated naturally or been killed by the watchdog should not 
affect the sub process.

However, it runs the risk of leaking threads. This may not seem much on a 
single ant run, but in an ant-in-gui or automated build system thread leakage 
can become an issue. Not as much a one as the build blocking, but still an 
issue.

I think therefore that for a patch like this to go into the build, it has to 
print out big warning messages to the effect that something is wrong with the 
client app. Also we need to see if anyone else has replicated the problem

--
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