You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2019/08/20 21:30:00 UTC
[jira] [Resolved] (SLING-8646) Remove LogService implementation
[ https://issues.apache.org/jira/browse/SLING-8646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-8646.
-------------------------------------
Resolution: Fixed
Implemented in rev 2d0b8df by removing the implementation and changing the slf4j support to a LogListener
> Remove LogService implementation
> --------------------------------
>
> Key: SLING-8646
> URL: https://issues.apache.org/jira/browse/SLING-8646
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: Commons Log Service 1.1.0
>
>
> As discussed on the mailing list, we should avoid implementing our own LogService, especially with the updates of R7 to the LogService specification this would mean to add a lot of new functionality.
> Therefore we should remove the LogService implementation from this bundle but keep logging to SLF4J through a LogListener service
--
This message was sent by Atlassian Jira
(v8.3.2#803003)