Hi all,

I experience some funny stuff with the "exec" task, when I set the "output"
attribute. It very much appears to me as if the output-stream does not get
flushed. Tried 1.5.3 and some 1.6's.

(I continue to have little luck with searching the bug-database; keep
getting lists a numbers out - probably a user-error - ...)

I suspect, that there is a "Runtime.exec()" hidden in there somewhere below
the "ExecTask". And some "Process.getOutputStream()". Instead I find lots of
OS-specific stuff (like direct invocation of "cmd.exe" instead of JNI with
::ShellExecuteEx() - well, fair enough!).

Where do I find the "Runtime.exec()" triggered by "ExecTask.execute()"?
I would like to have a closer look.

Have you ever discussed using a "SplitOutputStream" to have output from
"exec" guided to both a file and Ant-std-out at the same time - to see
progress while still preserving the information in a file - ? -Or a more
generic mechanism attached to Ant-std-out with tasks like "split-begin" and
"split-end"?

Hope one of you care to answer. :-)

Regards,
  Morten Sabroe Mortensen

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to