You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Emmanuel Bourg (JIRA)" <ji...@apache.org> on 2007/04/16 16:41:15 UTC
[jira] Updated: (CONFIGURATION-3) Drop 1st class dependency on
commons-logging
[ https://issues.apache.org/jira/browse/CONFIGURATION-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Bourg updated CONFIGURATION-3:
---------------------------------------
Fix Version/s: 2.0
Issue Type: Improvement (was: Bug)
Environment: (was: Operating System: All
Platform: Other)
Summary: Drop 1st class dependency on commons-logging (was: [configuration] Drop 1st class dependency on commons-logging)
> 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