[
https://jira.jboss.org/jira/browse/JBAS-7120?page=com.atlassian.jira.plug...
]
David Lloyd commented on JBAS-7120:
-----------------------------------
One way or another, this will only be fixed in 5.x, not in 6.x where it's an N/A
despite 6.0.0-M1 using commons-logging. In M2 and later, jcl-over-slf4j will take over.
In 5.x we should see if this can be fixed by switching back to the mainline JCL.
Patch commons-logging so that Jasper doesn't use a
deployment's logj4.jar when compiling a JSP in that deployment
-----------------------------------------------------------------------------------------------------------------
Key: JBAS-7120
URL:
https://jira.jboss.org/jira/browse/JBAS-7120
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Logging
Affects Versions: JBossAS-5.0.0.GA, JBossAS-5.0.1.GA, JBossAS-5.1.0.GA
Reporter: Jimmy Wilson
Assignee: David Lloyd
Attachments: commons-logging-1.1.0-jboss.diff-ur.patch
If a deployment (e.g. a WAR) packages its own log4j.jar then Jasper will use that
log4j.jar when compiling the deployment's JSPs. This can cause unexpected behavior.
Jasper should use JBoss' log4j.jar.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira