You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by ca...@apache.org on 2006/09/14 08:22:50 UTC
svn commit: r443261 - in /logging/log4j/trunk/src/xdocs: contributors.xml
documentation.xml download.xml history.xml plan.xml
Author: carnold
Date: Wed Sep 13 23:22:50 2006
New Revision: 443261
URL: http://svn.apache.org/viewvc?view=rev&rev=443261
Log:
Bug 40173: Update docs for log4j 1.3a9
Modified:
logging/log4j/trunk/src/xdocs/contributors.xml
logging/log4j/trunk/src/xdocs/documentation.xml
logging/log4j/trunk/src/xdocs/download.xml
logging/log4j/trunk/src/xdocs/history.xml
logging/log4j/trunk/src/xdocs/plan.xml
Modified: logging/log4j/trunk/src/xdocs/contributors.xml
URL: http://svn.apache.org/viewvc/logging/log4j/trunk/src/xdocs/contributors.xml?view=diff&rev=443261&r1=443260&r2=443261
==============================================================================
--- logging/log4j/trunk/src/xdocs/contributors.xml (original)
+++ logging/log4j/trunk/src/xdocs/contributors.xml Wed Sep 13 23:22:50 2006
@@ -19,6 +19,14 @@
<!-- ======================================== -->
<!-- LISTED IN ALPHABETICAL ORDER (last name) -->
<!-- ======================================== -->
+
+ <li><b>Curt Arnold</b>
+
+ <p>Curt is an independent software developer and current Logging Services PMC chair.
+ Curt developed the test framework for the W3C DOM test suites and has contributed to the
+ Apache Ant, Apache Xerces, Apache Batik, JSUnit, ArgoUML and ant-contrib
+ projects.</p>
+ </li>
<li><b>Mathias Bogaert</b>
Modified: logging/log4j/trunk/src/xdocs/documentation.xml
URL: http://svn.apache.org/viewvc/logging/log4j/trunk/src/xdocs/documentation.xml?view=diff&rev=443261&r1=443260&r2=443261
==============================================================================
--- logging/log4j/trunk/src/xdocs/documentation.xml (original)
+++ logging/log4j/trunk/src/xdocs/documentation.xml Wed Sep 13 23:22:50 2006
@@ -26,8 +26,8 @@
</p>
<p>
- <li>
- <b>javadoc: <a href="http://logging.apache.org/log4j/docs/api-1.2.13/index.html">1.2.13</a>, <a href="api-1.3.alpha9/index.html">1.3 alpha 9</a></b>
+ <li>
+ <b>javadoc: <a href="api/index.html">1.2.14</a>, <a href="http://logging.apache.org/log4j/docs/api-1.3/index.html">1.3 (alpha)</a></b>
</li>
</p>
Modified: logging/log4j/trunk/src/xdocs/download.xml
URL: http://svn.apache.org/viewvc/logging/log4j/trunk/src/xdocs/download.xml?view=diff&rev=443261&r1=443260&r2=443261
==============================================================================
--- logging/log4j/trunk/src/xdocs/download.xml (original)
+++ logging/log4j/trunk/src/xdocs/download.xml Wed Sep 13 23:22:50 2006
@@ -9,7 +9,7 @@
<meta name="keywords" content="java, log4j download, logging, tracing, component, framework, API, log4j"/>
<body>
- <section name="log4j version 1.2.13">
+ <section name="log4j version 1.2.14">
<p>Log4j is <a
href="http://logging.apache.org/site/binindex.cgi"><b>available
for download</b></a> from a number of mirrors. Please
@@ -17,9 +17,41 @@
bandwidth.
</p>
- <p>Log4j version 1.2.13 contains several bug fixes related to the TRACE
- level introduced in version 1.2.12 and a fix in the ConsoleAppender
- for a bug that affected JBoss.
+ <p>Changes in log4j 1.2.14:
+ <ul>
+ <li>AsyncAppender was rewritten to eliminate reported deadlocks (bugs <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=26224">26224</a>, <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=28006">28006</a>, <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=37904">37904</a>, <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=38137">38137</a>),
+ and to add an option to not block if the event queue becomes full (bug <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=38982">38982</a>).</li>
+
+ <li>SyslogAppender can now accept a port specification (bug <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=39687">39687</a>) in its syslogHost attribute.</li>
+
+ <li>SMPTAppender can now accept cc and bcc addresses (bug <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=19125">19125</a>) and perform password authentication (bug <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24969">24969</a>).</li>
+
+ <li>The following bugs were fixed:
+ <ul>
+ <li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=40159">40159</a>: NullPointerException in org.apache.log4j.NDC.get.
+ </li><li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=36787">36787</a>: org.apache.log4j.lf5.util.DateFormatManager.setTimeZone assignment error.
+ </li><li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=38559">38559</a>: Monthly logs not generated at midnight with DailyRollingFileAppender.
+ </li><li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=40145">40145</a>: PatternLayout specifier %r is not consistent with documentation.
+ </li><li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=37119">37119</a>: Space after log level causes default level to be used.
+ </li><li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=39135">39135</a>: Bad patterns in ISO8601DateFormat and DateTimeDateFormat.
+ </li><li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=35743">35743</a>: SyslogAppender throws NullPointerException upon misconfiguration.
+ </li><li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15501">15501</a>: FallbackErrorHandler throws NullPointerException if no loggers are set.
+ </li><li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=38564">38564</a>: Bad documentation for WriterAppender.encoding.
+ </li><li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=37866">37866</a>: NTEventLogAppender not build, tested and placed in distribution.
+ </li><li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=38662">38662</a>: SMTPAppender does not output newlines between stack trace lines.
+ </li><li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=30294">30294</a>: SMTPAppender will not run within sandbox.
+ </li><li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=16922">16922</a>: MDC with SMTPAppender doesn't work.
+ </li><li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=31507">31507</a>: Misspelling in HierarchyDynamicMBean.
+ </li><li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=35123">35123</a>: Additivity not exported by PropertyPrinter.
+ </li><li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=31003">31003</a>: RollingFileAppender, if removed, can cause NullPointerExceptions.
+ </li><li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=23021">23021</a>: AsyncAppender blocks on thread death.
+ </li><li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=40412">40412</a>: NOTICE file added to distribution and jar.
+ </li><li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=40378">40378</a>: Chainsaw of log4j 1.2 does not show TRACE level.
+ </li><li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=40501">40501</a>: TRACE level missing in short introduction to log4j.
+ </li><li><a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=37960">37960</a>: Update site generation to velocity 1.4 and remove dependency on logging/site project.
+ </li></ul>
+ </li>
+ </ul>
</p>
<p>The next major release of log4j will be version 1.3. It will contain
Modified: logging/log4j/trunk/src/xdocs/history.xml
URL: http://svn.apache.org/viewvc/logging/log4j/trunk/src/xdocs/history.xml?view=diff&rev=443261&r1=443260&r2=443261
==============================================================================
--- logging/log4j/trunk/src/xdocs/history.xml (original)
+++ logging/log4j/trunk/src/xdocs/history.xml Wed Sep 13 23:22:50 2006
@@ -9,6 +9,13 @@
<body>
<section name="Project history">
+
+ <p>The <a href="HISTORY"><b>project history</b></a> gives a
+ brief summary of changes and additions. Users frequently
+ report bugs that are solved in newer versions of log4j. Please
+ have a look at the history file before asking for help.
+ </p>
+
<p>The project's official URL is <a
href="http://logging.apache.org/log4j">http://logging.apache.org/log4j</a>.
</p>
Modified: logging/log4j/trunk/src/xdocs/plan.xml
URL: http://svn.apache.org/viewvc/logging/log4j/trunk/src/xdocs/plan.xml?view=diff&rev=443261&r1=443260&r2=443261
==============================================================================
--- logging/log4j/trunk/src/xdocs/plan.xml (original)
+++ logging/log4j/trunk/src/xdocs/plan.xml Wed Sep 13 23:22:50 2006
@@ -4,6 +4,7 @@
<properties>
<author email="not@disclosed">Ceki Gülcü</author>
<author email="not@disclosed">Mark Womack</author>
+ <author email="not@disclosed">Curt Arnold</author>
<title>Release roadmap for log4j</title>
</properties>
@@ -11,8 +12,7 @@
<section name="The Roadmap">
- <p>The log4j committers have adopted a roadmap for future releases
- of log4j. This page documents that roadmap and gives you an idea of what
+ <p>This page documents that roadmap and gives you an idea of what
to expect from future versions and timeframes for release.
</p>
@@ -29,258 +29,38 @@
</section>
- <section name="Release 1.2.X">
- <p>Expected timeframe: None</p>
+ <section name="Release 1.2.15">
+ <p>Expected timeframe: As needed</p>
- <p>No more releases on the 1.2.X codebase are currently planned. Efforts
- will now be focused on getting the 1.3 version shipped. However, if a
- critical bug fix is needed, another version will be released.
- </p>
+ <p>log4j 1.2.14 was released in September 2006. log4j 1.2 is continuing to be maintained
+ in response to reported, but no active development is anticipated in the near future. Backporting
+ the org.apache.log4j.rolling package from log4j 1.3 might be desirable since usage problems
+ with the original org.apache.log4j.RollingFileAppender and org.apache.log4j.DailyRollingFileAppender
+ are commonly reported.</p>
</section>
<section name="Release 1.3">
- <p>Expected timeframe: mid 2006</p>
-
- <p>The work for version 1.3 has been ongoing for a long time now, and it
- is time to button it up and let others take it for a ride. Reviewing,
- stablizing, and testing the 1.3 code for release is the major goal for
- the log4j committers for this year.
- </p>
-
- <p>Version 1.3 is going to contain some very extensive changes and new
- features. You should expect a number of api changes. Early release
- alpha versions have been available for a while, and the releases will be
- accelerating as the committers review and cleanup the current code base
- for release. As part of those releases, the committers plan to include
- jDiff reports that will clearly outline the changes and additions to the
- log4j code since the most recent 1.2.X release. This should help you in
- seeing what might need to be reviewed or fixed in your own code related
- to log4j.
- </p>
-
- <p>Below is a table from previous documentation about the 1.3 work plan
- and it is somewhat out of date. The committers will be updating this page
- with more and better documentation about what has changed, what has been
- reviewed, and what tasks remain as we work toward the 1.3 release.
- </p>
-
- <table class="ls" cellpadding="3" cellspacing="2">
-
- <tr>
- <th>Label</th>
- <th>Comment</th>
- <th>Volunteer</th>
- <th>Status</th>
- </tr>
-
- <tr bgcolor="DDDDDD">
- <td><b>test cases</b></td>
-
- <td>
- <p>Writing test cases is not the most sexy part of
- software development but it is one of the most
- important. Automated test cases allow us to catch bugs
- as early is possible. It is strongly recommended to add
- a new test case with each new feature or component.</p>
-
- <p>Existing <em>Perl</em> language based test cases have been
- migrated to junit (all-Java)based test
- cases. The new tests are placed under the
- <code>tests/</code> directory. It should be thus
- possible for participants in the project to understand
- the stucture of our tests and add tests for their
- components.
- </p>
- </td>
+ <p>Expected timeframe: indeterminate</p>
- <td>All committers</td>
- <td>ongoing effort</td>
- </tr>
-
- <tr>
- <td>Extensible XML configuration files</td>
-
- <td>
- <p>The DOMConfigurator is complex and not very
- flexible. It can only deal with elements that the
- developer knew about at compilation time. This has been
- an important drawback in the design of several appenders
- such as the the SMTPAppender and the
- RollingFileAppenders and its variants. These appenders
- need to delegate certain task to sub-components which
- are configured separately.
- </p>
-
- <p>The new JoranConfigurator being created by Ceki Gülcü will be based on
- a new 'module' know as Joran, which can convert XML files into other
- objects based on rules. You can read more abouth Joran <b><u>
- <a href="http://www.qos.ch/logging/JoranConfigurator.html">here</a>
- </u></b>
- </p>
- </td>
- <td>Ceki Gülcü</td>
- <td>Significantly progressed</td>
- </tr>
-
- <tr>
- <td>Log4j Domains</td>
-
- <td>
- <p>This is a very powerful and innovative concept that
- extends the notion of hierarchical loggers. It will also
- allow dynamic logging with pin-point accuracy. It was
- first suggested to me by Scott Stark of <a
- href="http://www.jboss.org">JBoss</a> fame.
- </p>
- </td>
- <td>Ceki Gülcü</td>
- <td>design board</td>
- </tr>
-
- <tr>
- <td>Multiple implementations of Logger</td>
-
- <td>
- <p>Based on <code>RepositorySelectors</code> introduced in
- log4j 1.2, the user will be able to replace the
- <code>Logger</code> implementation. Several
- implementations will be provided offering different
- properties and functionality although none of the
- implementations will add new public methods.
- </p>
- </td>
-
-
- <td>?</td>
- <td>vaporware</td>
- </tr>
- <tr>
- <td>Plugins/Receivers</td>
+ <p>Compatibility with earlier releases (as implied by a minor verion number change) was not enforced during the
+ development process and much of the recent effort has been to restore compatibility. However, it does not
+ seem likely that log4j 1.3 will ever been sufficiently compatible with log4j 1.2
+ to recommend it as a general replacement for log4j 1.2. Additional alpha releases are expected,
+ however it is possible that the development focus may shift to log4j 2.0.</p>
- <td>
- <p>A Plugin framework has been designed and implemented.</p>
- <p>All of the currently developed plugins are "Receivers", which can be
- thought of as the reverse of an appender; something
- that <b>accepts</b> LoggingEvents from some external source.
- </p>
- <p>This has proven particulaly useful with the log4j ports, with the
- addition of the XML-based Receivers able to accept
- LoggingEvents generated from other languages (see "Overture to other
- programming languages" below)
- </p>
-
- </td>
- <td>All</td>
- <td>Significantly progressed</td>
- </tr>
-
- <tr>
- <td>Improvements to Chainsaw</td>
-
- <td>
- <p><a href="chainsaw.html">Chainsaw v2</a> development has now progressed
- to the point where the main developers of it
- and many other members of the logging community are using it daily. It's
- still pre-alpha but only
- because we keep thinking up things to add.
- </p>
-
- </td>
- <td>Scott Deboy and Paul Smith</td>
- <td>Significantly progressed </td>
- </tr>
-
- <tr>
- <td>Custom conversion characters in PatternLayout</td>
- <td>Users often want to add new conversions characters or
- override the existing ones. This should be made easy using
- new configuration directives. This feature would use the
- extensions to XML configuration language mentioned
- above.</td>
-
- <td>Ceki Gülcü</td>
- <td>Completed, still testing</td>
- </tr>
-
- <tr>
- <td>Overture to other programming languages</td>
-
- <td><p>It is higly desriable to allow log4j ports in other languages
- to access log4j services in a language independent way. </p>
-
- <p>The use of a standard XML format to represent a LoggingEvent has been
- established and many of the related logging projects from
- non-Java languages have begun to support it. In fact, a number of the
- log4j ports have volunteered to join Apache!</p>
-
- <p>Scott Deboy has completed work to create a fex XML-based Receiver
- classes that can accept logging events from an external source, and
- 'import' them into the local log4j environment. </p> </td>
-
- <td>Ceki Gülcü, Scott Deboy</td>
- <td>Significantly Progressed (if not completed)</td>
- </tr>
-
- <tr>
- <td>Strategy based rollovers</td>
-
- <td>
- <p>Contrary to our own DailyRollingFileAppender, Avalon's
- logkit has a nice and clean implementation for rolling
- files. See the
- <code>org.apache.log.output.io.rotate</code> package for
- exact details.
- </p>
-
- <p>Their implementation is based on strategies which are
- sub-components of appender. We will be able to configure
- such sub-components with the new XML configuration
- scripts.
- </p>
- </td>
- <td>Ceki Gülcü</td>
- <td>Significantly Progressed</td>
- </tr>
-
-
-
- <tr>
- <td>Redesign of configure and watch architecture in
- configurators</td>
-
- <td>This is a very useful feature and the current architecture is not
- very good.
-
- <p>Contributions have been received by Mark Womack and others.</p>
-
- <p>See
- <pre>
- http://www.mail-archive.com/log4j-dev@jakarta.apache.org/msg01390.html
- http://www.mail-archive.com/log4j-user@jakarta.apache.org/msg00666.html
- http://marc.theaimsgroup.com/?t=101010070500002&r=1&w=2
- </pre>
- </p>
- </td>
- <td>Mark Womack</td>
- <td>initial implementation</td>
- </tr>
+ </section>
- <tr>
- <td>Performance improvements to LoggingEvent serialization</td>
-
- <td>
- <p>Ole Dalgaard has shown that by implementing the
- java.io.Externalizable interface instead of
- java.io.Serializable in the LoggingEvent class, the
- speed of serialiazation is increased by a factor of 4 or
- more.
- </p>
-
- </td>
- <td>Ole Dalgaard?</td>
- <td>initial implementation</td>
- </tr>
- </table>
+ <section name="Release 2.0">
+ <p>Expected timeframe: indeterminate</p>
+
+ <p>log4j 2.0 is still conceptual but would be designed for Java 5 and later,
+ would use be designed for fine-grain concurrency to maximize performance on
+ multi-processor systems, would minimize exposure of implementation details and
+ adhere to current Java coding practices. The design of log4j 2.0 may attempt to
+ support javax.util.logging by allowing, for example, a log4j 2.0 Appender to serve
+ as a javax.util.logging.Handler. log4j 2.0 would likely be modularized, possibly using
+ OSGi and would include a facade that emulates the log4j 1.3 API but would not be compatible
+ with user written appenders and other components.</p>
</section>
</body>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org