sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bertrand Delacretaz (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SLING-7611) Replace LogService with slf4j
Date Mon, 23 Apr 2018 12:46:00 GMT

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

Bertrand Delacretaz resolved SLING-7611.
----------------------------------------
       Resolution: Fixed
         Assignee: Bertrand Delacretaz
    Fix Version/s: Commons Mime 2.1.12

Pull request merged, thanks for your contribution!

> Replace LogService with slf4j
> -----------------------------
>
>                 Key: SLING-7611
>                 URL: https://issues.apache.org/jira/browse/SLING-7611
>             Project: Sling
>          Issue Type: Improvement
>          Components: Commons
>    Affects Versions: Commons Mime 2.1.10
>            Reporter: Christian Schneider
>            Assignee: Bertrand Delacretaz
>            Priority: Major
>             Fix For: Commons Mime 2.1.12
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently commons mime uses the LogService to log registered mime types. If no LogService
is available (like often in tests) it directly writes to stdout. In this case it is not possible
to configure what is logged.
> So I propose to switch this to slf4j. So this module works more like the other ones in
sling and the logging is easier to set up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message