From e628a3c9eb088f728c25941bef05bb73ea3feece Mon Sep 17 00:00:00 2001 From: Simon Kitching Date: Fri, 20 Jan 2006 10:21:26 +0000 Subject: [PATCH] Remove info about log4j 1.3, now that news has been received that it might not be incompatible after all. Remove deprecation info about class that has actually been removed. git-svn-id: https://svn.apache.org/repos/asf/jakarta/commons/proper/logging/trunk@370774 13f79535-47bb-0310-9956-ffa450edef68 --- RELEASE-NOTES.txt | 9 --------- 1 file changed, 9 deletions(-) diff --git a/RELEASE-NOTES.txt b/RELEASE-NOTES.txt index 83458d0..ae35a6a 100644 --- a/RELEASE-NOTES.txt +++ b/RELEASE-NOTES.txt @@ -161,10 +161,6 @@ favour of the "minimal" jarfile. == General Notes == -Log4J 1.3 is expected to include a binary-incompatible change from the 1.2 series that -unfortunately makes it impossible for a single adapter class to support both. -This release does not include support for Log4J 1.3. - The jakarta commons project has migrated to the Subversion version control system (previously, CVS was used). There should be no effect on users of the JCL library, but obviously the process of examining the latest source code, and of @@ -200,8 +196,3 @@ DEPRECATIONS: [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. -