ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject Re: cvs commit: ant/docs/manual/CoreTasks exec.html
Date Tue, 29 Jul 2003 14:40:21 GMT
On Tue, 29 Jul 2003, Antoine Levy-Lambert <>

> I do not know at all what is going to happen with output, error,
> stdin for the spawned process.

My guess is they cause trouble if the spawned process wants to use
them.  I should back that claim, maybe later today/tomorrow.

> I do not know how you implement OS specific redirections ?

I don't know either, I'd only know for Unix.

> I designed this to start something which is going to outlive ant,

Sure, I'm trying to improve upon it, that's all.

Now that you've made <exec> throw exceptions if the user combines
output with spawn (and it will be documented that way), we won't have
the user expect something wrong.  Now the user knows that she has to
tale care of the standard streams.

> I thought anyway that you do not want the output or error messages
> coming from the spawned process to pollute asynchronously the ant
> logs.

Certainly not, but you may want them to go to a file to review that
later or send them to /dev/null if you can't suppress output.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message