[ 
https://issues.apache.org/jira/browse/CONFIGURATION-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500695
 ] 

Thorbjørn Ravn Andersen commented on CONFIGURATION-3:
-----------------------------------------------------

I am currently working to migrate all our java code to use slf4j since that 
gives a very simple logging interface that we like.

They also have a package to directly redirect commons-loggging code to call 
slf4j which then in turn can call any supported logger.

Unfortunately commons configuration AbstractConfigurator class references the 
NoLog implementation package causing a runtime failure.

I suggest that the commons logging stuff could be replaced with sljf in the 
first place and make this much easier, and even be the one to make the patch if 
others want this too to get rid of interproject dependencies. 

> 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]

Reply via email to