commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONFIGURATION-614) Remove dependency to commons logging from API
Date Tue, 27 Oct 2015 08:42:27 GMT

    [ https://issues.apache.org/jira/browse/CONFIGURATION-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976016#comment-14976016
] 

Michael Osipov commented on CONFIGURATION-614:
----------------------------------------------

Why should we create another facade on top of a facade? That was made with Velocity and lead
to overhead and superfluous code. You need at most one facade. SFL4J works internally different
that ACL.

> 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)

Mime
View raw message