+1
What we really need now is a way to chain loggers together. My changes to
DefaultLogger made it subclassable at least, so I'd recommend that your
color logger subclass DefaultLogger (see MailLogger)
Any ideas on how to implement and specify from the command-line chainable
loggers?
Erik
----- Original Message -----
From: "Magesh Umasankar" <[EMAIL PROTECTED]>
To: "Ant Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, January 29, 2002 4:14 PM
Subject: ANSI Color Logger
> Hi,
> I have a custom logger that I like using
> every now and then when I perform a build
> in non-cron job mode.
>
> This custom logger uses ANSI color codes
> to distinguish various message levels -
> red for Project.MSG_ERR, of course ;-)
>
> It works on standard XTerms (Mindterm
> interface inclusive). It also works
> on Win9x as long as ANSI.SYS is loaded.
> It doesn't work on WinNT even with
> ANSI.SYS loaded and in command.com mode.
>
> The only use-case is that it is easier/
> faster to understand the output messages
> generated.
>
> Would it be of interest to you? If so,
> I can package it up (doc it, make it color
> configurable, etc.) and check it in as an
> additional logger.
>
> Cheers,
> Magesh
>
>
> ****************************************************
> * Atom Bomb: An invention to end all inventions. *
> ****************************************************
>
>
>
> --
> 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]>
