[jboss-jira] [JBoss JIRA] Commented: (JBAS-3348) Patch for JBAS-3347, %C log4j format problem

[Scott M Stark (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAS-3348?page=comments#action_12341589 ] 
            
Scott M Stark commented on JBAS-3348:
-------------------------------------

I don't see this error. When I run against a server with the updated commons-logging.jar the test passes:

[sstark at sstark testsuite]$ ant -Dtest=org.jboss.test.classloader.test.ScopingUnitTestCase -Dnojars=t  one-test
Buildfile: build.xml

one-test:
    [mkdir] Created dir: C:\svn\JBoss4.0\jboss-4.0.x\testsuite\output\log
    [junit] Running org.jboss.test.classloader.test.ScopingUnitTestCase
    [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 6.032 sec


> Patch for JBAS-3347, %C log4j format problem
> --------------------------------------------
>
>                 Key: JBAS-3348
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3348
>             Project: JBoss Application Server
>          Issue Type: Support Patch
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>    Affects Versions: JBossAS-4.0.4.GA
>            Reporter: Scott M Stark
>         Assigned To: Scott M Stark
>         Attachments: commons-logging.jar
>
>
> The %C classname format of the log4j pattern layout was broke by the 1.0.5.GA-jboss commons-logging release because the Log4jProxy was not using a FQCN that allowed the log4j LayoutInfo to find the caller. This has been corrected in the 1.0.5.SP1-jboss commons-logging release.

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