[
http://jira.jboss.com/jira/browse/JBTM-200?page=comments#action_12352837 ]
Jonathan Halliday commented on JBTM-200:
----------------------------------------
Repackaged Log4JLogger to our own package hierarchy and modified the factory classes
(JakartaLogFactory and JakartaRelevelingLogFactory) to install it via. setAttribute as
above. Tested using TestLevels class. Line number and class name is reported corretly.
org.apache class no longer appears in jbossts-common.jar. Committed as svn rev 9450, so
the fix should be part of TS 4.2.3.CR3 and later releases.
jbossts-common.jar includes commons-logging Log4JLogger
-------------------------------------------------------
Key: JBTM-200
URL:
http://jira.jboss.com/jira/browse/JBTM-200
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Scott M Stark
Assigned To: Jonathan Halliday
Fix For: 4.2.3
The jbossts-common.jar jar includes an implementation of the commons-logging Log
interface:
[starksm@succubus lib]$ jar -tf jbossts-common.jar | grep Log4
org/apache/commons/logging/impl/Log4JLogger.class
This cannot be included in jars bundled in jbossas as it conflicts with the commons
logging classes we bundle with the server. Either this needs to be extracted to a jar that
is not included, or simply an external dependency that requires a valid commons logging
jar.
--
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