commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (JIRA)" <>
Subject [jira] Resolved: (CONFIGURATION-3) [configuration] Drop 1st class dependency on commons-logging
Date Thu, 21 Dec 2006 21:03:22 GMT
     [ ]

Oliver Heger resolved CONFIGURATION-3.

    Resolution: Won't Fix

There is obviously not much interest in this issue any more, so I am closing it as wont't

The idea to allow a user setting a custom logger is not bad IMO. This functionality could
be implemented in AbstractConfiguration, per default a NoOpLog could be set. If this is desired,
please open a new enhancement request.

> [configuration] Drop 1st class dependency on commons-logging
> ------------------------------------------------------------
>                 Key: CONFIGURATION-3
>                 URL:
>             Project: Commons Configuration
>          Issue Type: Bug
>    Affects Versions: 1.2 Final
>         Environment: Operating System: All
> Platform: Other
>            Reporter: Joerg Schaible
>            Priority: Minor
> 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.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message