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 2010/09/10 10:44:32 UTC

[jira] Created: (SLING-1746) Use slf4j instead of log service

Use slf4j instead of log service
--------------------------------

                 Key: SLING-1746
                 URL: https://issues.apache.org/jira/browse/SLING-1746
             Project: Sling
          Issue Type: Task
    Affects Versions: OSGi Installer 3.0.0
            Reporter: Carsten Ziegeler
            Assignee: Carsten Ziegeler
            Priority: Minor
             Fix For: OSGi Installer 3.0.0


The installer uses currently the LogService to avoid dependencies - however nearly every log service implementation comes with various logging api's - so from
a dependency pov it's no difference.
The slf4j api (or any other logging api) provides more usuability, therefore we should switch

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


[jira] Updated: (SLING-1746) Use slf4j instead of log service

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler updated SLING-1746:
------------------------------------

    Component/s: Installer

> Use slf4j instead of log service
> --------------------------------
>
>                 Key: SLING-1746
>                 URL: https://issues.apache.org/jira/browse/SLING-1746
>             Project: Sling
>          Issue Type: Task
>          Components: Installer
>    Affects Versions: OSGi Installer 3.0.0
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Minor
>             Fix For: OSGi Installer 3.0.0
>
>
> The installer uses currently the LogService to avoid dependencies - however nearly every log service implementation comes with various logging api's - so from
> a dependency pov it's no difference.
> The slf4j api (or any other logging api) provides more usuability, therefore we should switch

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


[jira] Resolved: (SLING-1746) Use slf4j instead of log service

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-1746.
-------------------------------------

    Resolution: Fixed

Switched with revision 995732


> Use slf4j instead of log service
> --------------------------------
>
>                 Key: SLING-1746
>                 URL: https://issues.apache.org/jira/browse/SLING-1746
>             Project: Sling
>          Issue Type: Task
>    Affects Versions: OSGi Installer 3.0.0
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Minor
>             Fix For: OSGi Installer 3.0.0
>
>
> The installer uses currently the LogService to avoid dependencies - however nearly every log service implementation comes with various logging api's - so from
> a dependency pov it's no difference.
> The slf4j api (or any other logging api) provides more usuability, therefore we should switch

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