http://bugzilla.slf4j.org/show_bug.cgi?id=22
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2006-06-08 21:08 -------
The fact that removing
META-INF/services/org.apache.commons.logging.LogFactory from
jcl104-over-slf4j.jar makes the problem go away confirms my previous
suspicion about commons-logging-api.jar kicking in instead of
jcl104-over-slf4j.jar. (Several servlet containers treat
org.apache.commons.logging.* classes specially by imposing parent
first class loading delegation model for JCL classes.)
To cut a long story short, I will make a new release of SLF4J which
will stop throwing an exception when the
o.a.c.l.impl.SLF4FLogFactory#release method is called. Instead, the
method will issue a warning with a link to
http://www.slf4j.org/codes.html
I would appreciate if you could verify that the new release behaves as expected.
--
Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
dev mailing list
[email protected]
http://slf4j.org/mailman/listinfo/dev
