You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by sk...@apache.org on 2006/01/22 09:07:58 UTC

svn commit: r371232 - /jakarta/commons/proper/logging/trunk/RELEASE-NOTES.txt

Author: skitching
Date: Sun Jan 22 00:07:54 2006
New Revision: 371232

URL: http://svn.apache.org/viewcvs?rev=371232&view=rev
Log:
Add more info on commons-logging-adapters.jar file.

Modified:
    jakarta/commons/proper/logging/trunk/RELEASE-NOTES.txt

Modified: jakarta/commons/proper/logging/trunk/RELEASE-NOTES.txt
URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/logging/trunk/RELEASE-NOTES.txt?rev=371232&r1=371231&r2=371232&view=diff
==============================================================================
--- jakarta/commons/proper/logging/trunk/RELEASE-NOTES.txt (original)
+++ jakarta/commons/proper/logging/trunk/RELEASE-NOTES.txt Sun Jan 22 00:07:54 2006
@@ -52,7 +52,13 @@
 
 * New jarfile commons-logging-adapters-xxx.jar is now provided. This can be
   used to resolve class cast conflicts where parts of commons-logging are
-  deployed via different classloaders.
+  deployed via different classloaders. It is not expected to be frequently
+  used; it is only necessary in situations where a container has deployed
+  commons-logging-api.jar and a webapp wants to bind to a third-party
+  logging implementation such as log4j. In this case, the webapp can
+  experience problems if it deploys commons-logging.jar as this causes
+  duplicates of the core commons-logging classes, but commons-logging-adapters
+  can be safely used.
 
 * New internal diagnostics feature. If commons-logging is behaving in an
   unexpected manner, you can now set system property



---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org