You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Oliver Heger (JIRA)" <ji...@apache.org> on 2015/11/14 16:57:11 UTC
[jira] [Resolved] (CONFIGURATION-614) Remove dependency to commons
logging from API
[ https://issues.apache.org/jira/browse/CONFIGURATION-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver Heger resolved CONFIGURATION-614.
----------------------------------------
Resolution: Fixed
The reference to Commons Logging has been removed from the Configuration API. Fixed in SVN in revision 1714340.
> Remove dependency to commons logging from API
> ---------------------------------------------
>
> Key: CONFIGURATION-614
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-614
> Project: Commons Configuration
> Issue Type: Improvement
> Affects Versions: 1.9
> Reporter: Oliver Heger
> Fix For: 2.0
>
>
> Commons Configuration uses Commons Logging as logging framework (which is fine).
> Some methods of the public API reference logger objects; for instance, a specific logger can be set for each configuration instance. This is problematic because the logging framework cannot be changed without breaking binary compatibility. Even if there was a new major release of Commons Logging, we could not switch to this new version.
> As a solution a minimum logging abstraction can be created, e.g. a class {{ConfigurationLogger}}. This class can be exposed in the public API. Internally, it still delegates to Commons Logging.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)