src/xdocs/download.xml - logging-log4j1 - Git at Google

 <?xml version="1.0"?>
 <document>

   <properties>
     <author email="ceki@apache.org">Ceki Gulcu</author>
     <title>Download</title>
   </properties>

   <meta name="keywords" content="java, logging, tracing, component, framework, API, log4j"/>
 <body>

     <section name="log4j version 1.2.8">
       <p>log4j 1.2.8 is available in <a
 	href="../jakarta-log4j-1.2.8.tar.gz"><b>TAR.GZ</b></a> format
 	or in <a href="../jakarta-log4j-1.2.8.zip"><b>ZIP</b></a>
 	format.
       </p>

       <p>As of release 1.2.8 log4j now searches for the file log4j.xml
         as well as the file log4j.properties during
         initialization. See the <a href="HISTORY">HISTORY</a> file for
         the firther details.
       </p>

       <p>In addition to many performance improvements, bug fixes, and
 	other small enhancements, log4j 1.2 adds JMX support, Mapped
 	Diagnostic Contexts, JDBC logging, graphical log viewer
 	(chainsaw), and buffered IO capability. One important change
 	is the replacement of the <code>Category</code> class with
 	<code>Logger</code> class and the <code>Priority</code> class
 	with the <code>Level</code> class in order to facilitate
 	migrating from the JDK 1.4 logging API to log4j. <a
 	href="http://www.javaworld.com/javaworld/jw-05-2001/jw-0504-finalists.html"><img
 	src="images/ecaward_finalist_logo.gif" align="right"
 	border="0"/></a>
       </p>

 	<p>Version 1.2 is the 22nd major public release of log4j.  All
 	changes except the removal of deprecated methods are backward
 	compatible such that log4j 1.2 can be considered a drop in
 	replacement for log4j 1.1.3. The only exception is the
 	renaming of the <code>CategoryFactory</code> class to
 	<code>LoggerFactory</code> class such that subclasses of
 	<code>Category</code> class must be modified and
 	recompiled. <em>The recommended pattern for extending the
 	<code>Logger</code> class is wrapping. Moreover, we strongly
 	discourage casual users from subclassing the
 	<code>Category</code> or <code>Logger</code> classes. </em>
       </p>

       <p>We also maintain a list of <a href="earlier.html">earlier
 	  versions</a> of log4j for download, intended for the curious
 	  paleontologist -- there seems to be quite a few of them!
       </p>


     </section>


     <section name="Third-party extensions (listed in alphabetical order)">

       <dl>

 	<!-- ============================================================================== -->

 	<dt><a
 	href="http://logui.sourceforge.net/"><b>Chainsaw</b></a></dt>
 	<dd><b>Chainsaw is now integrated with log4j and ships with
 	the official distribution.</b> Chainsaw is a graphical log
 	viewer and filter for the log4j package. It listens for <a
 	href="http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/spi/LoggingEvent.html">LoggingEvent</a>
 	objects sent using the <a
 	href="http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/net/SocketAppender.html">SocketAppender</a>
 	and displays them in a table. Chainsaw also supports loading
 	events from files in <code>XMLLayout</code> format.
 	</dd>

 	<!-- ============================================================================== -->

 <!--	<dt><a href="http://www.japhy.de/configLog4j"><b>configLog4j</b></a></dt>

 	<dd>A graphical log4j configuration editor by Tobias
 	Dezulian.</dd>
 -->
 	<!-- ============================================================================== -->

 	<dt>
 	  <a
 	href="http://www.mannhaupt.com/danko/projects/"><b>JDBCAppender</b></a>
 	</dt>

         <dd>A powerful <code>JDBCAppender</code> by Danko Mannhaupt
 	  who continues the work of Thomas Fenner. You might find
 	  this JDBCAppender more suitable then the one that ships with
 	  log4j 1.2.
 	</dd>

 	<!-- ============================================================================== -->

 	<dt><a href="http://qos.ch/"><b>log4j<em>ME</em></b></a></dt>

 	<dd>Log4j<em>ME</em>, or log4j MiniEdition, is based on the
 	same code as log4j. However, as the name indicates the
 	mini-edition is much smaller. It offers the same client
 	interface such that code compiled for log4jME is 100%
 	compatible with log4j standard edition. You can choose to
 	upgrade to log4j standard edition at any time by replacing
 	<em>log4jME.jar</em> with <em>log4j.jar</em> in your
 	classpath.
 	</dd>

 	<!-- ============================================================================== -->

 	<dt><a href="http://www.launchsoftware.com"><b>LogWeb</b></a> (commercial) </dt>

 	<dd>Log4Web is a J2EE web application, designed to web-enable
 	  system log files that have been generated by log4j.
 	</dd>

 	<!-- ============================================================================== -->

 	<dt><a
 	    href="http://traxel.com/lumbermill/"><b>Lumbermill</b></a></dt>
 	<dd>Lumbermill is a Swing(tm) log processing and distribution
 	  system for Log4j. </dd>

 	<!-- ============================================================================== -->

 	<dt>
 	  <a
 	href="http://www.servidium.com/site/logfactor5/index.html"><b>LogFactor5</b>
 	</a>(commercial)
 	</dt>

 	<dd>Another full-featured graphical log viewer. After a merger
 	  and the subsequent change in business-orientation, the
 	  owners of LogFactor5 have decided to donate their product to
 	  the log4j project.
 	</dd>

 	<!-- ============================================================================== -->

 	<dt><a href="http://jakarta.apache.org/taglibs/doc/log-doc/intro.html">
 	    <b>Log Tag</b></a>
 	</dt>
 	<dd>A custom log tag library from the <a
 	    href="http://jakarta.apache.org/taglibs/index.html">Jakarta
 	    Taglibs</a> project.</dd>

 	<!-- =========================================================================== -->

 	<dt><a href="http://www.m2technologies.net/asp/snmpTrapAppender.asp">
 	    <b>SNMPTrapAppender</b></a>
 	</dt>

 	<dd>An appender to send formatted logging event strings to a
 	  specified managment host (typically, a MLM of some sort, but
 	  could also be an SNMP management console) in the form of an
 	  SNMP trap.
 	</dd>

 	<!-- =========================================================================== -->

       </dl>
     </section>

     <section name="Ports to other languages">

       <dl>
 	<!-- =========================================================================== -->
 	<dt><a
 	href="http://log4c.sourceforge.net"><b>log4c</b></a></dt>

 	<dd>ANSI C functions and macros for flexible logging to files
 	and other destinations. It is modeled after log4j. It follows
 	the log4j API within the limits of reason. Intended for use in time-space
 	critical environments.</dd>

 	<!-- =========================================================================== -->

 	<dt><a
 	href="http://sourceforge.net/projects/log4cpp/"><b>log4cpp</b></a></dt>
 	<dd>A library of C++ classes for flexible logging to files,
 	syslog, IDSA and other destinations modeled after log4j.</dd>

 	<!-- ========================================================================== -->

 	<dt><a
 	href="http://log4cplus.sourceforge.net/"><b>log4cplus</b></a></dt>
 	<dd>A competing port to C++.</dd>

 	<!-- =========================================================================== -->

 	<dt><a
 	href="http://goanna.sourceforge.net/"><b>log4E</b></a></dt>

 	<dd>The Goanna project (Eiffel Web Services) now includes
 	log4E, a complete port of log4j.
 	</dd>

 	<!-- =========================================================================== -->
 	<dt><a
 	href="http://log4perl.sourceforge.net"><b>Log::Log4perl</b></a></dt>

 	<dd>Log::Log4perl is a Perl port of log4j by Kevin Goess and
 	Mike Schilli. The authors made sure that their port was as
 	close as possible to the original implementation.  Even the
 	configuration files are similar! The project is still being
 	enhanced, however the current release is stable and has been
 	released to CPAN.
 	</dd>
 	<!-- =========================================================================== -->
 	<dt><a
 	href="http://www.neoworks.com/products/log4net/"><b>log4net</b></a></dt>

 	<dd>The .NET implementation of the popular log4j Java API
 	providing flexible and arbitrarily granular control over log
 	management and configuration.</dd>

 	<!-- =========================================================================== -->
 	<dt><a
 	href="http://www.its4you.at/log4py.php"><b>log4py</b></a></dt>

 	<dd>Log4Py is a python logging module similar to log4j. It
 	supports logging to files or to stdout/stderr, variable
 	log-levels, configurable output formats and configuration via
 	configuration files.
 	</dd>

 	<!-- =========================================================================== -->

 	<dt><a
 	href="http://log4p.sourceforge.net"><b>log4p</b></a></dt>
 	<dd>Another Python translation of log4j. This project no
 	longer seems to be maintained.</dd>

 	<!-- =========================================================================== -->

 	<dt><a href="http://log4plsql.sourceforge.net/"><b>log4plsql</b></a></dt>

 	<dd>Log4plsql is a Oracle PL/SQL logging module similar to
 	log4j. It supports logging out-off transaction. It is useful
 	for logging, benchmarking and monitoring PL/SQL applications.
 	</dd>

 	<!-- =========================================================================== -->

 	<dt><a href="http://sourceforge.net/projects/qmmslog"><b>qmmslog</b></a></dt>

 	<dd>Qmmslog is a port of log4j to the Qt/C++ platform.
 	</dd>

 	<!-- =========================================================================== -->
 	<dt><a
 	href="http://log4r.sourceforge.net"><b>log4r</b></a></dt>
 	<dd>A Powerful Logger for Ruby.
 	  <p>Log4r features an extremely flexible logging library for
 	    Ruby. Killer features include a heiarchial logging system
 	    of any number of levels, logger inheritance, multiple
 	    output destinations, tracing, custom formatting and more.
 	    Log4r was inspired by log4j. Log4r provides the defining
 	    features of log4j and some of its own features that just
 	    might make log4j users envious.</p>
 	</dd>

 	<!-- =========================================================================== -->
       </dl>


       <p>If you would like your software to be listed here, then send a note to the <a
 	  href="mailto:log4j-user@jakarta.apache.org">log4j-user@jakarta.apache.org</a>
 	list.</p>

     </section>

   </body>
 </document>
	<?xml version="1.0"?>
	<document>

	<properties>
	<author email="ceki@apache.org">Ceki Gulcu</author>
	<title>Download</title>
	</properties>

	<meta name="keywords" content="java, logging, tracing, component, framework, API, log4j"/>
	<body>

	<section name="log4j version 1.2.8">
	<p>log4j 1.2.8 is available in <a
	href="../jakarta-log4j-1.2.8.tar.gz"><b>TAR.GZ</b></a> format
	or in <a href="../jakarta-log4j-1.2.8.zip"><b>ZIP</b></a>
	format.
	</p>

	<p>As of release 1.2.8 log4j now searches for the file log4j.xml
	as well as the file log4j.properties during
	initialization. See the <a href="HISTORY">HISTORY</a> file for
	the firther details.
	</p>

	<p>In addition to many performance improvements, bug fixes, and
	other small enhancements, log4j 1.2 adds JMX support, Mapped
	Diagnostic Contexts, JDBC logging, graphical log viewer
	(chainsaw), and buffered IO capability. One important change
	is the replacement of the <code>Category</code> class with
	<code>Logger</code> class and the <code>Priority</code> class
	with the <code>Level</code> class in order to facilitate
	migrating from the JDK 1.4 logging API to log4j. <a
	href="http://www.javaworld.com/javaworld/jw-05-2001/jw-0504-finalists.html"><img
	src="images/ecaward_finalist_logo.gif" align="right"
	border="0"/></a>
	</p>

	<p>Version 1.2 is the 22nd major public release of log4j. All
	changes except the removal of deprecated methods are backward
	compatible such that log4j 1.2 can be considered a drop in
	replacement for log4j 1.1.3. The only exception is the
	renaming of the <code>CategoryFactory</code> class to
	<code>LoggerFactory</code> class such that subclasses of
	<code>Category</code> class must be modified and
	recompiled. <em>The recommended pattern for extending the
	<code>Logger</code> class is wrapping. Moreover, we strongly
	discourage casual users from subclassing the
	<code>Category</code> or <code>Logger</code> classes. </em>
	</p>

	<p>We also maintain a list of <a href="earlier.html">earlier
	versions</a> of log4j for download, intended for the curious
	paleontologist -- there seems to be quite a few of them!
	</p>


	</section>


	<section name="Third-party extensions (listed in alphabetical order)">

	<dl>

	<!-- ============================================================================== -->

	<dt><a
	href="http://logui.sourceforge.net/"><b>Chainsaw</b></a></dt>
	<dd><b>Chainsaw is now integrated with log4j and ships with
	the official distribution.</b> Chainsaw is a graphical log
	viewer and filter for the log4j package. It listens for <a
	href="http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/spi/LoggingEvent.html">LoggingEvent</a>
	objects sent using the <a
	href="http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/net/SocketAppender.html">SocketAppender</a>
	and displays them in a table. Chainsaw also supports loading
	events from files in <code>XMLLayout</code> format.
	</dd>

	<!-- ============================================================================== -->

	<!-- <dt><a href="http://www.japhy.de/configLog4j"><b>configLog4j</b></a></dt>

	<dd>A graphical log4j configuration editor by Tobias
	Dezulian.</dd>
	-->
	<!-- ============================================================================== -->

	<dt>
	<a
	href="http://www.mannhaupt.com/danko/projects/"><b>JDBCAppender</b></a>
	</dt>

	<dd>A powerful <code>JDBCAppender</code> by Danko Mannhaupt
	who continues the work of Thomas Fenner. You might find
	this JDBCAppender more suitable then the one that ships with
	log4j 1.2.
	</dd>

	<!-- ============================================================================== -->

	<dt><a href="http://qos.ch/"><b>log4j<em>ME</em></b></a></dt>

	<dd>Log4j<em>ME</em>, or log4j MiniEdition, is based on the
	same code as log4j. However, as the name indicates the
	mini-edition is much smaller. It offers the same client
	interface such that code compiled for log4jME is 100%
	compatible with log4j standard edition. You can choose to
	upgrade to log4j standard edition at any time by replacing
	<em>log4jME.jar</em> with <em>log4j.jar</em> in your
	classpath.
	</dd>

	<!-- ============================================================================== -->

	<dt><a href="http://www.launchsoftware.com"><b>LogWeb</b></a> (commercial) </dt>

	<dd>Log4Web is a J2EE web application, designed to web-enable
	system log files that have been generated by log4j.
	</dd>

	<!-- ============================================================================== -->

	<dt><a
	href="http://traxel.com/lumbermill/"><b>Lumbermill</b></a></dt>
	<dd>Lumbermill is a Swing(tm) log processing and distribution
	system for Log4j. </dd>

	<!-- ============================================================================== -->

	<dt>
	<a
	href="http://www.servidium.com/site/logfactor5/index.html"><b>LogFactor5</b>
	</a>(commercial)
	</dt>

	<dd>Another full-featured graphical log viewer. After a merger
	and the subsequent change in business-orientation, the
	owners of LogFactor5 have decided to donate their product to
	the log4j project.
	</dd>

	<!-- ============================================================================== -->

	<dt><a href="http://jakarta.apache.org/taglibs/doc/log-doc/intro.html">
	<b>Log Tag</b></a>
	</dt>
	<dd>A custom log tag library from the <a
	href="http://jakarta.apache.org/taglibs/index.html">Jakarta
	Taglibs</a> project.</dd>

	<!-- =========================================================================== -->

	<dt><a href="http://www.m2technologies.net/asp/snmpTrapAppender.asp">
	<b>SNMPTrapAppender</b></a>
	</dt>

	<dd>An appender to send formatted logging event strings to a
	specified managment host (typically, a MLM of some sort, but
	could also be an SNMP management console) in the form of an
	SNMP trap.
	</dd>

	<!-- =========================================================================== -->

	</dl>
	</section>

	<section name="Ports to other languages">

	<dl>
	<!-- =========================================================================== -->
	<dt><a
	href="http://log4c.sourceforge.net"><b>log4c</b></a></dt>

	<dd>ANSI C functions and macros for flexible logging to files
	and other destinations. It is modeled after log4j. It follows
	the log4j API within the limits of reason. Intended for use in time-space
	critical environments.</dd>

	<!-- =========================================================================== -->

	<dt><a
	href="http://sourceforge.net/projects/log4cpp/"><b>log4cpp</b></a></dt>
	<dd>A library of C++ classes for flexible logging to files,
	syslog, IDSA and other destinations modeled after log4j.</dd>

	<!-- ========================================================================== -->

	<dt><a
	href="http://log4cplus.sourceforge.net/"><b>log4cplus</b></a></dt>
	<dd>A competing port to C++.</dd>

	<!-- =========================================================================== -->

	<dt><a
	href="http://goanna.sourceforge.net/"><b>log4E</b></a></dt>

	<dd>The Goanna project (Eiffel Web Services) now includes
	log4E, a complete port of log4j.
	</dd>

	<!-- =========================================================================== -->
	<dt><a
	href="http://log4perl.sourceforge.net"><b>Log::Log4perl</b></a></dt>

	<dd>Log::Log4perl is a Perl port of log4j by Kevin Goess and
	Mike Schilli. The authors made sure that their port was as
	close as possible to the original implementation. Even the
	configuration files are similar! The project is still being
	enhanced, however the current release is stable and has been
	released to CPAN.
	</dd>
	<!-- =========================================================================== -->
	<dt><a
	href="http://www.neoworks.com/products/log4net/"><b>log4net</b></a></dt>

	<dd>The .NET implementation of the popular log4j Java API
	providing flexible and arbitrarily granular control over log
	management and configuration.</dd>

	<!-- =========================================================================== -->
	<dt><a
	href="http://www.its4you.at/log4py.php"><b>log4py</b></a></dt>

	<dd>Log4Py is a python logging module similar to log4j. It
	supports logging to files or to stdout/stderr, variable
	log-levels, configurable output formats and configuration via
	configuration files.
	</dd>

	<!-- =========================================================================== -->

	<dt><a
	href="http://log4p.sourceforge.net"><b>log4p</b></a></dt>
	<dd>Another Python translation of log4j. This project no
	longer seems to be maintained.</dd>

	<!-- =========================================================================== -->

	<dt><a href="http://log4plsql.sourceforge.net/"><b>log4plsql</b></a></dt>

	<dd>Log4plsql is a Oracle PL/SQL logging module similar to
	log4j. It supports logging out-off transaction. It is useful
	for logging, benchmarking and monitoring PL/SQL applications.
	</dd>

	<!-- =========================================================================== -->

	<dt><a href="http://sourceforge.net/projects/qmmslog"><b>qmmslog</b></a></dt>

	<dd>Qmmslog is a port of log4j to the Qt/C++ platform.
	</dd>

	<!-- =========================================================================== -->
	<dt><a
	href="http://log4r.sourceforge.net"><b>log4r</b></a></dt>
	<dd>A Powerful Logger for Ruby.
	<p>Log4r features an extremely flexible logging library for
	Ruby. Killer features include a heiarchial logging system
	of any number of levels, logger inheritance, multiple
	output destinations, tracing, custom formatting and more.
	Log4r was inspired by log4j. Log4r provides the defining
	features of log4j and some of its own features that just
	might make log4j users envious.</p>
	</dd>

	<!-- =========================================================================== -->
	</dl>


	<p>If you would like your software to be listed here, then send a note to the <a
	href="mailto:log4j-user@jakarta.apache.org">log4j-user@jakarta.apache.org</a>
	list.</p>

	</section>

	</body>
	</document>