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 (Closed) (JIRA)" <ji...@apache.org> on 2012/02/07 15:53:00 UTC

[jira] [Closed] (SLING-2224) Split Commons Log Bundle

     [ https://issues.apache.org/jira/browse/SLING-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed SLING-2224.
-----------------------------------

    
> Split Commons Log Bundle
> ------------------------
>
>                 Key: SLING-2224
>                 URL: https://issues.apache.org/jira/browse/SLING-2224
>             Project: Sling
>          Issue Type: Improvement
>          Components: Commons
>    Affects Versions: Commons Log 2.1.2
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: Commons Log Service 1.0.0, Commons Log 3.0.0
>
>         Attachments: split-commons-log.patch
>
>
> To leverage OSGi modularization and to easier manage the evolution of the Sling logging infrastructure the existing Sling Commons Log bundle should be split as follows:
>   * Use slf4j-api, jcl-over-slf4j, log4j-over-slf4j as separate bundles
>   * Create a new bundle Commons Log Service implementing just the OSGi LogService over slf4j
>   * Keep just the configuration support, slfj4 implementation, and the JUL bridge in the Commons Log Bundle
> See also http://markmail.org/message/f2bv6lulc6mdxdue

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