[jira] Commented: (CONFIGURATION-3) Drop 1st class dependency on commons-logging

["Oliver Heger (JIRA)" <ji...@apache.org>]

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

Oliver Heger commented on CONFIGURATION-3:
------------------------------------------

Should a generic library like Commons Configuration really depend on a specific logging library? I think log4j is still in wide use, and if an application that uses this library wanted to include a dependency to Configuration, there would be two logging implementations to be handled.

But my knowledge about logging implementations is a bit outdated. This may not be a problem these days any more.

> 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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org