[jira] Closed: (SLING-143) Replace internal Logger interface with Felix Framework Logger

["Felix Meschberger (JIRA)" <ji...@apache.org>]

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

Felix Meschberger closed SLING-143.
-----------------------------------

    Resolution: Fixed

Implemented in Rev. 605865 (launcher/app) and 605866 (launcher/webapp).

> Replace internal Logger interface with Felix Framework Logger
> -------------------------------------------------------------
>
>                 Key: SLING-143
>                 URL: https://issues.apache.org/jira/browse/SLING-143
>             Project: Sling
>          Issue Type: Improvement
>          Components: Launcher
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 2.0.0
>
>
> The Sling launcher currently defines its own (simple) Logger interface to log bootstrap messages. The Felix framework also has an internal Logger used for logging. This latter Logger is able to switch over to using the OSGi LogService as soon as such a service is available.
> It would of course be good, if Sling launcher and the Felix framework could use the same Logger for logging. The basis for this functionality has been laid out with the recent implementation of issue FELIX-428, which enables injecting a Logger instance in to the Felix framework for shared use between Felix and the launcher.
> So we can now adapt the Sling launcher to actually provide such logger instances and therefore drop our internal Logger interface.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.