You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (Resolved) (JIRA)" <ji...@apache.org> on 2011/10/02 16:09:33 UTC
[jira] [Resolved] (SLING-1867) Use existing SLF4J SPI
implementation
[ https://issues.apache.org/jira/browse/SLING-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved SLING-1867.
--------------------------------------
Resolution: Duplicate
Assignee: Felix Meschberger
Closing as duplicate
> Use existing SLF4J SPI implementation
> -------------------------------------
>
> Key: SLING-1867
> URL: https://issues.apache.org/jira/browse/SLING-1867
> Project: Sling
> Issue Type: Task
> Components: Commons
> Affects Versions: Commons Log 2.1.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
>
> Currently the commons/log module uses a private implementation of the SLF4J SPI to provide logging to the console or to log files. In that respect we provide a small subset of the functionality or more complete SLF4J SPI implementations like logback or nlog4j.
> We should probably consider to drop our implementation and instead use Log4J (somewhat older but offers more appenders and is an ASF project widely used and supported) or LogBack (more modern but offers less appenders)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira