The MailLogger captures all output logged through DefaultLogger (standard Ant
-output) and will send success and failure messages to unique e-mail lists, with
+
The MailLogger captures all output logged through DefaultLogger (standard Ant
+output) and will send success and failure messages to unique e-mail lists, with
control for turning off success or failure messages individually.
@@ -161,22 +167,97 @@ control for turning off success or failure messages individually.
+
+
+The AnsiColorLogger adds color to the standard Ant output
+by prefixing and suffixing ANSI color code escape sequences to
+it. It is just an extension of DefaultLogger
+and hence provides all features that DefaultLogger does.
+AnsiColorLogger differentiates the output by assigning
+different colors depending upon the type of the message.
+If used with the -logfile option, the output file
+will contain all the necessary escape codes to
+display the text in colorized mode when displayed
+in the console using applications like cat, more, etc.
+This is designed to work on terminals that support ANSI
+color codes. It works on XTerm, ETerm, Win9x Console
+(with ANSI.SYS loaded.), etc.
+NOTE:
+It doesn't work on WinNT even when a COMMAND.COM console loaded with
+ANSI.SYS is used.
+If the user wishes to override the default colors
+with custom ones, a file containing zero or more of the
+custom color key-value pairs must be created. The recognized keys
+and their default values are shown below:
+AnsiColorLogger.ERROR_COLOR=2;31
+AnsiColorLogger.WARNING_COLOR=2;35
+AnsiColorLogger.INFO_COLOR=2;36
+AnsiColorLogger.VERBOSE_COLOR=2;32
+AnsiColorLogger.DEBUG_COLOR=2;34
+Each key takes as value a color combination defined as
+Attribute;Foreground;Background. In the above example, background
+value has not been used.
+This file must be specfied as the value of a system variable
+named ant.logger.defaults and passed as an argument using the -D
+option to the java command that invokes the Ant application.
+An easy way to achieve this is to add -Dant.logger.defaults=
+/path/to/your/file to the ANT_OPTS environment variable.
+Ant's launching script recognizes this flag and will pass it to
+the java command appropriately.
+Format:
+AnsiColorLogger.*=Attribute;Foreground;Background
+
+Attribute is one of the following:
+0 -> Reset All Attributes (return to normal mode)
+1 -> Bright (Usually turns on BOLD)
+2 -> Dim
+3 -> Underline
+5 -> link
+7 -> Reverse
+8 -> Hidden
+
+Foreground is one of the following:
+30 -> Black
+31 -> Red
+32 -> Green
+33 -> Yellow
+34 -> Blue
+35 -> Magenta
+36 -> Cyan
+37 -> White
+
+Background is one of the following:
+40 -> Black
+41 -> Red
+42 -> Green
+43 -> Yellow
+44 -> Blue
+45 -> Magenta
+46 -> Cyan
+47 -> White
+
+
+
+ant -logger org.apache.tools.ant.listener.AnsiColorLogger
+
+
+
-Passes build events to Log4j, using the full classname's of the generator of
+
Passes build events to Log4j, using the full classname's of the generator of
each build event as the category:
- build started / build finished - org.apache.tools.ant.Project
- target started / target finished - org.apache.tools.ant.Target
- task started / task finished - the fully qualified classname of the task
- - message logged - the classname of one of the above, so if a task logs a
+
- message logged - the classname of one of the above, so if a task logs a
message, its classname is the category used, and so on.
-All start events are logged as INFO. Finish events are either logged as
-INFO or ERROR depending on whether the build failed during that stage. Message
-events are logged according to their Ant logging level, mapping directly to a
+
All start events are logged as INFO. Finish events are either logged as
+INFO or ERROR depending on whether the build failed during that stage. Message
+events are logged according to their Ant logging level, mapping directly to a
corresponding Log4j level.
@@ -187,7 +268,7 @@ corresponding Log4j level.
-Writes all build information out to an XML file named log.xml, or the value
+
Writes all build information out to an XML file named log.xml, or the value
of the XmlLogger.file property if present.
@@ -198,18 +279,18 @@ of the XmlLogger.file property if present.
-See the Build Events section for
+
See the Build Events section for
developers.
Notes:
- - A listener or logger should not write to standard output or error - Ant
+
- A listener or logger should not write to standard output or error - Ant
captures these internally and may cause an infinite loop.
-Copyright © 2001 Apache Software Foundation. All rights
+
Copyright © 2002 Apache Software Foundation. All rights
Reserved.