[
http://jira.jboss.com/jira/browse/JBAS-2823?page=all ]
Scott M Stark resolved JBAS-2823.
---------------------------------
Resolution: Done
A 1.1.0.jboss release of commons-logging has been added to the repository and tagged with
JBoss_Apache_Common_Logging_1_1_0 in the
:ext:starksm@cvs.forge.jboss.com:/cvsroot/jboss apache/commons-logging cvs module. The
repository includes the source as commons-logging-src.zip.
An additional
org.jboss.test.classloader.test.ScopingUnitTestCase.testWarCommonsLoggingWithCLJarLog4jOverrides
test has been added so that the log4j factory is validated both without and with the
commons-logging.jar in the war WEB-INF/lib.
This has been tested with the commons logging package filter removed from the
jboss-web.deployer, so the filter has been dropped as well.
Upgrade commons-logging to v1.1
-------------------------------
Key: JBAS-2823
URL:
http://jira.jboss.com/jira/browse/JBAS-2823
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Logging
Affects Versions: JBossAS-4.0.2 Final, JBossAS-4.0.3 Final, JBossAS-4.0.3 SP1
Environment: Windows XP Professional, JDK 1.5.0
Reporter: Martin Lui
Assigned To: Scott M Stark
Fix For: JBossAS-4.2.0.CR1
The Apache commons-logging package has release version 1.1.0.
Please upgrade this library to take advantage of items listed in the release notes:
http://jakarta.apache.org/commons/logging/RELEASE-NOTES.txt
It would be helpful if this upgrade can be done to upgrade the server libraries since
individual EAR files cannot overwrite this particular library.
Also, looking through the notes and searching for information on the 1.0.4 patch, it
appears that the WeakHashTables memory-leak fix is included in 1.1.0. (Bug 31286:
http://issues.apache.org/bugzilla/show_bug.cgi?id=31286)
Depending on how JBoss uses this package, upgrading should be as simple as replacing the
current package (though I admit I had not try doing so yet).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira