[ http://issues.apache.org/jira/browse/CONFIGURATION-3?page=all ]
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 fix. 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: http://issues.apache.org/jira/browse/CONFIGURATION-3 > 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 > http://issues.apache.org/bugzilla/show_bug.cgi?id=38929 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]