Home → Repo ^aEp6o → Branch v1_2_15_rc1 Files → src → xdocs → download.xml

The version of Apache log4j used by SoundHelix.
[[ 🗃 ^aEp6o apache-log4j ]] :: [📥 Inbox] [📤 Outbox] [🐤 Followers] [🤝 Collaborators] [🛠 Commits]
Clone

HTTPS: git clone https://vervis.peers.community/repos/aEp6o
SSH: git clone USERNAME@vervis.peers.community:aEp6o
Branches

trunk
download.xml

<?xml version="1.0" encoding="iso-8859-1"?>
<!--
 Licensed to the Apache Software Foundation (ASF) under one or more
 contributor license agreements.  See the NOTICE file distributed with
 this work for additional information regarding copyright ownership.
 The ASF licenses this file to You under the Apache License, Version 2.0
 (the "License"); you may not use this file except in compliance with
 the License.  You may obtain a copy of the License at

      http://www.apache.org/licenses/LICENSE-2.0

 Unless required by applicable law or agreed to in writing, software
 distributed under the License is distributed on an "AS IS" BASIS,
 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.

-->
<document>

  <properties>
    <author email="not@disclosed">Ceki G�lc�</author>
    <title>Download</title>
  </properties>

    <meta name="keywords" content="java, log4j download, logging, tracing, component, framework, API, log4j"/>
      <body>
	
      <section name="log4j version 1.2.15">
	  <p>Log4j is <a
	      href="http://logging.apache.org/site/binindex.cgi"><b>available
	      for download</b></a> from a number of mirrors. Please
	      use these mirrors as they improve download time and save
	      bandwidth.
	  </p>
	  
	  <p>Changes in log4j 1.2.15:
    <ul>
  <li>SyslogAppender now supports a "header" property which if true, causes the appender to produce the HEADER part (timestamp and hostname) of the syslog
  packet.  Default value is false for compatibility with previous behavior.  The SyslogAppender also now sends any header from the associated layout when
  activateOptions is called or the first logging event is send and any footer when the appender is closed.</li>
 
  <li>NTEventLogAppender: Updated NTEventLogAppender.dll which corrects missing event messages
        and which should work with earlier releases of log4j.  If replacing
        a previously used NTEventLogAppender.dll, the registry key 
        HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Eventlog/Application/Log4J
        should be removed to allow the new DLL to properly register itself.</li>

  <li>The following bugs were fixed:
      <ul>
       <li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=40944">40944</a>: PropertyConfigurator.configure(URL) does not close resource stream.</li>
       <li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=40937">40937</a>: In Turkish locale level "info" is not equivalent to "INFO"</li>
       <li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=41339">41339</a>: Javadoc of PatternLayout should use %n in TTCC layout examples</li>
       <li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=41219">41219</a>: Stacktraces of exceptions disappear occassionally</li>
       <li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=38680">38680</a>: Incorrect message when specified custom level class does not implement toLevel</li>
       <li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=37282">37282</a>: SyslogAppender leaks descriptors</li>
       <li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=41040">41040</a>: SyslogAppender should prefix message with TIMESTAMP and local hostname</li>
       <li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=40502">40502</a>: SyslogAppender assumes all lines start with tab</li>
       <li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=41169">41169</a>: NTEventLogAppender.dll :: "missing" event description</li>
       <li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=41487">41487</a>: Warning when configuring inner-class logger</li>
       <li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=41186">41186</a>: AsyncAppender in 1.2.14 DiscardSummary events create NullPointerExceptions in layouts</li>
       <li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=37864">37864</a>: Add target to generate binary and source compatibility report</li>
       <li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=41708">41708</a>: PropertyPrinter.printOptions breaking signature change in log4j 1.2.9</li>
      </ul>
   </li>
    </ul>
    </p>

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

	</section>


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

      <dl>

	<!-- ============================================================================== -->
	<dt><a href="http://minaret.biz/tips/datedFileAppender.html"><b>DatedFileAppender</b></a></dt>

	<dd><code>DatedFileAppender</code> works in the same manner as
	the Tomcat FileLogger. Contrary to
	<code>DailyRollingFileAppender</code> shipping with log4j, log
	file names generated by <code>DatedFileAppender</code> always
	contain today's date. While this distinction seems minor, it
	means you can reliably copy, compress, remove or manipulate a
	day's log file shortly after midnight. With the
	<ocde>DailyRollingFileAppender</ocde>, a day's log file is not
	renamed until the first message is logged some time after
	midnight.
	</dd>

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

	<dt>
	  <a
	href="http://www.dankomannhaupt.de/projects/index.html"><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://just4log.sf.net/"><b>Just4log</b></a>
	</dt> 

        <dd>Just4Log is a library to enhance dynamically the
        performance of various logging systems inside a java
        application. Dynamically because the sourcecode in java is not
        modified but rather the optimization occurs on the compiled
        ByteCode files.
	</dd>

     <!-- ============================================================================== -->	
	<dt><a href="http://purl.net/jware/antx/"><b>log4Ant</b></a></dt>

	<dd>log4Ant includes a complete bridge to the Log4J logging systemfor a robust build monitoring system. 
	These Ant components let you capture, map, and send Ant log messages and stdio output through your Log4J installation.  Contact <a href="maito:contact@jware.info">contact@jware.info</a>
        </dd>
     <!-- ============================================================================== -->	

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

	<dd>Log4J400 includes MessageQueue and DataQueue Appenders for
	the AS/400 (aka IBM iSeries).
        </dd>

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

	<dd>This Project provides a set of EJBs to store Log4J events
	(received via JMS appender) in a database. The main aim is to
	provide a toolset for a centralized, data-center suitable
	logging.
        </dd>

	<!-- ============================================================================== -->	
	
	<dt><a href="http://svn.apache.org/viewcvs.cgi/logging/sandbox/log4j/log4jMini/trunk/"><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
	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. At this time, log4jME is only available through
	ASF Subversion repository in the Logging Services Sandbox.
	</dd>
	
       <!-- ============================================================================== -->	
	
	<dt><a href="http://www.openfuture.de/Log4Unit/"><b>log4<em>Unit</em></b></a></dt>

	<dd>Log4Unit is a <a
	href="http://www.junit.org/index.htm">JUnit</a> extension
	combining JUnit with Log4J. The intention is to create test
	protocols for JUnit.

        <p>JUnit is asymmetrical in the sense that it focusses on the
        documentation of test failures and errors. Successful
        execution of a test case is not further documented. In order
        to obtain a test protocol that documents the initial settings,
        the test case execution and its results, a logging component
        is required. Log4J as the current de facto standard is
        selected for this extension.
        </p>
	</dd>

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

	<dt><a href="http://www.launchsoftware.com"><b>Log4Web</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://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.codeczar.com/products/logweb/index.html"><b>LogWeb</b></a> </dt>

	<dd>LogWeb is a web interface for configuring log4j at runtime
	within a servlet container.  Every log4j feature of is
	configurable through this interface.
	</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>

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

         <dt><a href="http://xpolog.com"><b>XpoLog</b></a>
	</dt>

	<dd>Log view and analysis application which enables web
	browsing and analysis over logs.
	</dd>

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

      </dl>
    </section>
    
    <section name="Ports to other languages (listed in alphabetical order within each section)">

     <subsection name="Fellow Apache Logging Services Projects">

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

	<dt><a
	href="http://logging.apache.org/log4cxx/"><b>log4cxx</b></a></dt>
	<dd>Log4cxx is a port to C++ of the log4j project.</dd>

	<!-- =========================================================================== -->	
	<dt><a
	href="http://logging.apache.org/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://logging.apache.org/log4php/"><b>log4php</b></a></dt> 

        <dd>Log4Php is a PHP port of log4j framework. It supports xml configuration,
        logging to files, stdout/err, syslog, socket, configurable
        output layouts and logging levels. </dd>

     </dl>
    </subsection>

    <subsection name="Other Ports">
     <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>Log4cplus is a simple to use C++ logging API providing
	thread-safe, flexible, and arbitrarily granular control over
	log management and configuration. It is modeled after the Java
	log4j API.</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://log4ls.sourceforge.net/"><b>log4LS</b></a></dt>

        <dd>Log4LS is a LotusScript library package and is used to get
         logging statements to a Domino database, sent by mail or
         written to a file. It is modeled after Jakarta log4j.
         </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>

     </subsection>
      
      <p>If you would like your software to be listed here, then send a note to the <a
	  href="mailto:log4j-user@logging.apache.org">log4j-user@logging.apache.org</a>
	list.</p>
      
    </section>
    
  </body>
</document>
[See repo JSON]
Clone

Branches

Tags

download.xml
