JWare/AntXtras Log4Ant
                     Version 2.0.0, Release Dec 2009
                   -----------------------------------

                            
This document contains the major Log4Ant version change notes. For the most
recent information, visit the website at http://antxtras.sourceforge.net.

------------------------------------------------------------------------------
This version of Log4Ant is the initial extraction of the old AntXtras 
0.5x feedback components to a new independent project based on the new
v2 AntXtras library. This project replaces the old AntXtras feedback 
components completely.

This initial standalone release of Log4Ant contains significant design
changes to the original. In particular, Log4Ant v2 is now based on the
SLF4J not Log4J. SLF4J supports Log4J as well as several other logging
systems out-of-the-box. Additionally, Log4Ant can now expose much more
of your Ant static and dynamic fixture in a way that is easily married 
with your logging system's configuration methods.


=> Before using Log4Ant, you must decide what your *real* logging 
   system will be. Log4Ant's "_bin_withdeps" comes setup to work with
   Log4J; but you can easily replace the "slf4j-log4j12" libraries
   with Logback, JCL, or something else. Whatever your choice, make
   sure the system's required configuration is in you ANT CLASSPATH.

   EXAMPLE: Defining Log4Ant to use Logback as its logging system.

    <project xmlns:emit="jware.log4ant"...>
      ...
      <taskdef uri="jware.log4ant"
          resource="org/jwaresoftware/log4ant/antlib-ns.xml">
        <classpath>
          <fileset dir="${LOG4ANT_HOME}/dep">
            <include name="antxtras/lib/*.jar"/>
            <include name="slf4j/lib/*.jar"/>
            <include name="logback/lib/*.jar"/>
          </fileset>
          <fileset dir="${LOG4ANT_HOME}/lib">
            <include name="jw-log4ant.jar"/>
          </fileset>
        </classpath>
      </taskdef>
      <emit:checkpoint message="SUCCESS" status="G"/>
      ...
    </project>


=> If you're going to use the <emit:checkpoint> component, you should
   configure a "TICKS" logger in your logging system. Typically you
   only need to include the script location and the output message
   (which has time and status embedded so no need to include those).

   EXAMPLE: Log4J properties configuration for the "TICKS" logger:
   
     log4j.appender.TICKS.layout.ConversionPattern=%X{.location}: %m%n


   EXAMPLE: Logback configuration for the "TICKS" logger:
   
    <appender name="TICKS" class="ch.qos.logback.core.ConsoleAppender">
      <layout class="ch.qos.logback.classic.PatternLayout">
        <Pattern>%X{.location}: %m%n</Pattern>
      </layout>
    </appender>


-SSMC