From: "Dominique Devienne" <[EMAIL PROTECTED]>
Reply-To: "Ant Users List"
To: "Ant Users List"
Subject: RE: How to supress output
Date: Fri, 21 Jan 2005 14:56:51 -0600
>
> Pretty much; it goes through a lot of pain to set up
> the ExecuteStreamHandler used by the Execute.
So assuming the ClearCas
From: "Dominique Devienne" <[EMAIL PROTECTED]>
Reply-To: "Ant Users List"
To: "Ant Users List"
Subject: RE: How to supress output
Date: Fri, 21 Jan 2005 14:09:33 -0600
> From: Russell Johannesson [mailto:[EMAIL PROTECTED]
>
> It occurs to me that t
It occurs to me that the problem under discussion isn't necessarily specific
to ClearCase. Wouldn't any task which employs Runtime.exec() internally
potentially be a source of unwanted output? Would it be reasonable to
request that there be control over the exec output of all such tasks? That
w
ommitter ? Since the project is open
source, isn't anyone who contributes to the code a developer?
-Rob Anderson
> -Original Message-
> From: Russell Johannesson [mailto:[EMAIL PROTECTED]
> Sent: Thursday, January 20, 2005 5:18 PM
> To: user@ant.apache.org
> Subject
I recently raised a similar issue for ClearCase. In fact, I submitted an
enhancement request.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33169
One developer responded that no one had ClearCase, and so they couldn't test
such a change even if they made it. Perhaps this issue could be addre
Thanks for your reply. The output occurs whether or not the "log" attribute
is specified. The output is a list of each directory processed by the
update. The log file is more of a summary. We have no problem with the log
file. We just want to suppress the other output.
From: "Anderson, Rob (Glo
The ClearCase "ccupdate" task writes too much to the standard output. I
can't seem to stop it from printing each directory in the update. The
ClearCase ccupdate task is ultimately implemented as a command-line exec, so
it seems that ant doesn't control the output. I'm wondering if this notion
i
