[jbossts-issues] [JBoss JIRA] Closed: (JBTM-380) update log4j to mach JBossAS

Wed Jun 25 09:36:28 EDT 2008

     [ http://jira.jboss.com/jira/browse/JBTM-380?page=all ]

Jonathan Halliday closed JBTM-380.
----------------------------------

    Resolution: Done

> update log4j to mach JBossAS
> ----------------------------
>
>                 Key: JBTM-380
>                 URL: http://jira.jboss.com/jira/browse/JBTM-380
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Application Server Integration
>    Affects Versions: 4.3.0.GA
>            Reporter: Jonathan Halliday
>         Assigned To: Jonathan Halliday
>             Fix For: 4.4.CR1
>
>
> JBossAS uses a slightly different log4j release from the one we have. Although it's only a point release it does contain a public API change (Level.TRACE) which can cause problems with certain classpath settings. Upgrade JBossTS to use the same log4j.jar as the app server, thus eliminating this annoyance.

-- 
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