You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Oliver Heger (JIRA)" <ji...@apache.org> on 2006/06/24 18:05:30 UTC
[jira] Commented: (CONFIGURATION-3) [configuration] Drop 1st class
dependency on commons-logging
[ http://issues.apache.org/jira/browse/CONFIGURATION-3?page=comments#action_12417640 ]
Oliver Heger commented on CONFIGURATION-3:
------------------------------------------
What's the status of this issue? Is there still a desire to drop the commons logging dependency?
I had a look at the places where logging is used. Some of them are unnecessary IMO. But for the following places we would need an aquivalent replacement:
- ConfigurationFactory logs optional configurations that cannot be loaded. Maybe we could add a method to ConfigurationFactory that checks whether an optional configuration source could be loaded or not.
- ConfigurationUtils.locate() logs the location from where a configuration file was loaded. Not sure if this makes too much sense: If a configuration has been successfully loaded, its URL can be checked. OTH it would be very useful when a configuration file could not be found to throw an exception that contains all the paths where it was searched for. However this won't be easy to implement.
- JNDIConfiguration and DatabaseConfiguration swallow some exceptions and write them to the log. Here we would have to find an alternative. Maybe introduce a mode, in which such exceptions are re-thrown as runtime exceptions?
> [configuration] Drop 1st class dependency on commons-logging
> ------------------------------------------------------------
>
> Key: CONFIGURATION-3
> URL: http://issues.apache.org/jira/browse/CONFIGURATION-3
> Project: Commons Configuration
> Type: Bug
> 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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org