In Ant 1.6.3 (final, not beta) or CVS HEAD you can
conditionally define a redirector, giving it an id:
for no file,
for a
file.
and use it with your :
-Matt
--- Ninju Bohra <[EMAIL PROTECTED]> wrote:
> Can you give a further detail on how to use the
> solution (having never used
> s
>
--- Ninju Bohra <[EMAIL PROTECTED]> wrote:
> While waiting for a fix (which will
> neccesiate a move to 1.6.3) I wonder if I can use
> to solve my problem (though maybe not as
> elegently).
Elegant enough.
>
> Define a presetdef for each for the standard
> (console output) invocation. Inside
While waiting for a fix (which will
neccesiate a move to 1.6.3) I wonder if I can use
to solve my problem (though maybe not as
elegently).
Define a presetdef for each for the standard
(console output) invocation. Inside the main script
use a simple check on the presence of an
${output.file} p
--- Ninju Bohra <[EMAIL PROTECTED]> wrote:
> Oops,
>
> Look like the "spawn" attribute route won't work :-)
>
> With "spawn=true" the task does NOT "block"
> and
> wait for the executable to finish. I need to have
> the
> script proceed only after the execuatable is
> finished,
> so we down to
Oops,
Look like the "spawn" attribute route won't work :-)
With "spawn=true" the task does NOT "block" and
wait for the executable to finish. I need to have the
script proceed only after the execuatable is finished,
so we down to the and/or moving to 1.6.3
--- Ninju Bohra <[EMAIL PROTECTED]>
Can you give a further detail on how to use the
solution (having never used s
before)?
I am using ANT 1.6.2 (can't use 1.6.3beta1 :-()
Taking Ivan Ivanov's advice I would like to have the
output from the either come to the screen (when
run by user) or go to file (when invoked by CC) based
upon
I guess spawn could work. A couple more options:
You want to have a single task declaration that uses
options. Meaning you can't just declare file without
using it all the time. So you have two choices, still
using I/O redirection. With Ant 1.6.3 you will have
the alwayslog attribute on a redir
I thought about using the output attribute, but what
value would I use for when they DO want the output to
come to the console? I don't want to have the
task duplicated (differing only in one have the
output="NUL" and the other not using the output
attribute) and then a set of conditions controll
I would suggest you save the output to an
external log file and if CruiseControl permits it
attach the log file to its email. Thus it will not
mess up the email but you will also be able to inspect
it if something go wrong.
Regards
Ivan
--- Ninju Bohra <[EMAIL PROTECTED]> wrote:
> Hello all,
>
--- Matt Benson <[EMAIL PROTECTED]> wrote:
> If you are using a recent version of Ant, you could
> redirect to your null device (a file).
Actually this should work even with not-so-recent Ant
versions.
-Matt
__
Do you Yahoo!?
Make Yahoo! your h
If you are using a recent version of Ant, you could
redirect to your null device (a file). Since you're
on Windows (I assume from the backslashed paths), the
file will be NUL . You could do some conditional
stuff based on OS to choose NUL or /dev/null as your
null device and be cross-platform, bu
Hello all,
On my Windows Box, I have a series of calls to
do a set of Orcale database operations, one of the
calls look like:
Now everyt
12 matches
Mail list logo
