Stefan,
My patch to DefaultLogger (still sitting in the queue somewhere) addresses
this somewhat allowing a DefaultLogger subclass to grab what is being logged
and do whatever it likes with it, so a subclass could write a file and still
see the results. Not to mention the fact that we could (and I have... its
waiting for my DefaultLogger patch to go through) obsolete the e-mail build
results FAQ entry..... I have a MailLogger that still outputs to the console
and e-mails the results at the end.
Erik
----- Original Message -----
From: "Stefan Bodewig" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, December 07, 2001 8:53 AM
Subject: Re: Antwort: Re: How to use BuildLogger?
> On Fri, 7 Dec 2001, Anton Grimm <[EMAIL PROTECTED]> wrote:
>
> > actually I want to log on stdout and additionally see the same
> > output in a log-file.
>
> A tee(1) BuildLogger would be handy, yes. Unfortunately there is
> nothing like this ATM. Only the main logger is allowed to print to
> the screen and you cannot pass a filename to DefaultLogger when you
> use it as a BuildListener.
>
> You could use XmlLogger as a listener - but this is going to give you
> XML output (it will print to log.xml or the file whose name is given
> by the property XmlLogger.file).
>
> The only other option I see is a custom logger/listener.
>
> Stefan
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
