Siphalor/tweed5-commons-logging
1
0
Fork 0
Code Activity

Add LOGGING-114, LOGGING-115 and LOGGING-117 to the release notes.

Browse Source 
git-svn-id: https://svn.apache.org/repos/asf/commons/proper/logging/trunk@595102 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Dennis Lundberg
2007-11-14 22:42:14 +00:00
parent 576e85c122
commit aefdc85e6a
1 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
RELEASE-NOTES.txt
View File

@@ -130,11 +130,15 @@ Logging with Maven 1.x will be removed in a future version of Commons Logging.
Commons Logging library was not sufficient as an AccessController was not used. Commons Logging library was not sufficient as an AccessController was not used.
This has been fixed by catching SecurityException and using an AccessController. This has been fixed by catching SecurityException and using an AccessController.
* LOGGING-111: Show the contents of chained exceptions, to make debugging easier, * LOGGING-111, LOGGING-114: Show the contents of chained exceptions, to make
in particular when using Commons Logging together with Log4J. debugging easier, in particular when using Commons Logging together with Log4J.
* LOGGING-113: pom.xml in maven repository does not list dependencies as optional. * LOGGING-113: pom.xml in maven repository does not list dependencies as optional.
* LOGGING-115: NPE thrown due to exception message logging.
* LOGGING-117: Unit tests fail on linux with java16.
* MEV-392 (http://jira.codehaus.org/browse/MEV-392) * MEV-392 (http://jira.codehaus.org/browse/MEV-392)
As Commons Logging didn't provide a Maven2 pom.xml file, one was helpfully As Commons Logging didn't provide a Maven2 pom.xml file, one was helpfully
created by people not involved with the commons-logging project and published created by people not involved with the commons-logging project and published