[
https://issues.apache.org/jira/browse/CONFIGURATION-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490758
]
Emmanuel Bourg commented on CONFIGURATION-3:
--------------------------------------------
It's still possible to use Log4J with the Java logging API, it's as simple as
writing a custom Filter or Handler redirecting every log call to Log4J. I'm
surprised Log4J doesn't provide such a bridge by default. I have found one
example of a Filter doing this :
http://www.fedora.info/download/2.2/javadocs/fedora/utilities/Log4JRedirectFilter.html
> Drop 1st class dependency on commons-logging
> --------------------------------------------
>
> Key: CONFIGURATION-3
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-3
> Project: Commons Configuration
> Issue Type: Improvement
> Affects Versions: 1.2
> Reporter: Joerg Schaible
> Priority: Minor
> Fix For: 2.0
>
>
> Currently commons-logging is reported as first class dependency in the project
> reports. This is not true. The only classes that make direct usage of JCL are
> ConfigurationDynaBean/Class and this only for tracing. It would be nice to
> eliminate this reference at all and list JCL only as transitive dependency of
> digester and beanutils.
> We might support logging with the monitor/listener concept of
> http://issues.apache.org/bugzilla/show_bug.cgi?id=38929
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
