commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: jakarta-commons/logging RELEASE-NOTES.txt
Date Fri, 04 Apr 2003 02:49:10 GMT
craigmcc    2003/04/03 18:49:10

  Modified:    logging  RELEASE-NOTES.txt
  Update release notes for a proposed 1.0.3 release of Commons Logging.
  Revision  Changes    Path
  1.2       +74 -8     jakarta-commons/logging/RELEASE-NOTES.txt
  Index: RELEASE-NOTES.txt
  RCS file: /home/cvs/jakarta-commons/logging/RELEASE-NOTES.txt,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- RELEASE-NOTES.txt	29 Jan 2002 20:31:04 -0000	1.1
  +++ RELEASE-NOTES.txt	4 Apr 2003 02:49:10 -0000	1.2
  @@ -1,23 +1,89 @@
                              Commons Logging Package
  -                                Version 1.0
  -                               Release Notes
  +                                Version 1.0.3
  +                                Release Notes
   This document contains the release notes for this version of the Commons
  -Logging package. This is the first release of commons-logging.
  +Logging package.  It is primarily a maintenance and code cleanup release,
  +with minimal new features.
  +The following paragraphs document changes since the previous release
  +(version 1.0.2).
  -* commons-logging implements an abstraction between logging and the logging 
  -  implementation being used.  You can currently use Avalon's logkit, Log4J, 
  -  JDK 1.4's logging, or nothing at all.  It is up to you.
  +[build.xml]        Refined build process to correctly avoid compiling classes
  +                   when dependencies are not available, and to avoid name
  +                   clashes over Ant properties used in different ways.
  +[unit tests]       Added new suites of tests for the Log4J and JDK 1.4
  +                   logging implementations, including tests with multiple
  +                   class loaders that closely simulate the scenario of using
  +                   commons-logging in a servlet container.
  +[documentation]    Overall cleanup and correction of the JavaDoc documentation
  +                   to correctly reflect the current behavior.  In particular,
  +                   the default logging implementation (selected if nothing
  +                   else is configured) is now SimpleLog, not NoOpLog.
  +[LogFactory]       Add a static release(ClassLoader) method that allows,
  +                   for example, a webapp to clean up all c-l references
  +                   prior to being shut down.
  +[build.xml]        Correct the META-INF/MANIFEST.MF that was embedded in the
  +                   generated JAR files to properly contain the version number.
  +[LogFactory]       Fix security violations on several ClassLoader method
  +                   invocations.
  +[SimpleLog]        Dump stack trace through logger, instead of directly to
  +                   System.out, to preserve output sequence.
  +[SimpleLog]        Avoid a security exception if system properties cannot be
  +                   read (such as in an applet).
  +[Bugzilla 10825]   NullPointerException when Logger.getClassLoader()
  +                   returns null.
  +[Bugzilla 13118]   Correct detection of JDK 1.4 that was mis-identifying on a
  +                   scenario where a JDK 1.3 implementation included an
  +                   implementation of JSR-47 logging.
  +[Bugzilla 13157]   Incorrect selection of Log4J in a servlet container.
  +[Bugzilla 13201]   Log4JLogger should not attempt to auto-configure
  +                   appenders; this is out of scope for commons-logging.
  +[Bugzilla 17561]   Attempts to override Log4J configuration.
  +[Bugzilla 17894]   Unable to configure commons-logging SimpleLog for a webapp.
  +[Bugzilla 18184]   Jdk14Logger should not waste the effort to create a
  +                   Throwable (to extract calling class and method) if the
  +                   message is not going to be logged anyway.
  +[LogSource]        Previously deprecated, replaced by LogFactory.
  +[Log4jFactory]     A proxy instance of this class was transparently created
  +                   when Log4J logging was selected, yet it serves no useful
  +                   purpose.  The class is now deprecated, and the proxy
  +                   instance is no longer created.
  +[Log4JCategoryLog] This class has been replaced by Log4JLogger, which
  +                   corresponds to the availability of the new Logger class
  +                   in Log4J 1.2 and later.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message