commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Bourg (JIRA)" <>
Subject [jira] Commented: (CONFIGURATION-3) Drop 1st class dependency on commons-logging
Date Sun, 22 Apr 2007 23:29:15 GMT


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 :

> Drop 1st class dependency on commons-logging
> --------------------------------------------
>                 Key: CONFIGURATION-3
>                 URL:
>             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

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:
For additional commands, e-mail:

View raw message