https://issues.apache.org/bugzilla/show_bug.cgi?id=42855
Thorbjørn Ravn Andersen <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #1 from Thorbjørn Ravn Andersen <[EMAIL PROTECTED]> 2008-08-02
12:34:48 PST ---
If I understand your issue correctly, your problem is that you WANT to use
log4j but the log4j loading inside commons-logging fails due to missing
classes.
Personally I would suggest you stop using commons-logging and instead use slf4j
with the log4j backend (this is a simple compile-time binding without class
loader voodoo) and add the commons-logging slf4j module to satisfy your current
commons-logging calls.
See http://slf4j.org/docs.html for documentation.
As an added benefit it gives you the ability to use {} in your log strings as
object.toString() placeholders. This allow you to get rid of many
logger.isDebugEnabled() calls. See
http://slf4j.org/faq.html#logging_performance
I do not think that this is a bug in log4j, and certainly not one which
warrants adding try-catch stuff to the static init part of LogManager. Please
reopen issue if you disagree.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
