DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=28565>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28565 org.apache.tools.ant.taskdefs.Execute [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2004-04-23 22:24 ------- Gus: PumpedStreamHandler makes use of StreamPumper objects. These can be constructed to automatically close the streams or not. The output streams are not closed by PumpedStreamHandler's use of StreamPumpers, by design. One question I have: what do you mean by Execute task? Do you mean the Execute class (not a task) or the ExecTask class (which is a task) --? ExecTask, for example, uses a Redirector helper object to take care of the Process I/O, and it is in this Redirector's complete() method that the relevant streams are closed. If you are using the Execute class from your own code, then indeed, yes, you need to close your streams however you see fit, and creating your own ExecuteStreamHandler implementation is certainly one valid solution. But I'm not going to count any of this as a problem until I see evidence that one or more of the core tasks is not closing the stream. Please add a comment if this is, after all, the case. Thanks, Matt --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
