You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Matteo Merli (JIRA)" <ji...@apache.org> on 2017/05/10 21:16:04 UTC

[jira] [Resolved] (BOOKKEEPER-1059) Upgrade to SLF4J-1.7.25

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

Matteo Merli resolved BOOKKEEPER-1059.
--------------------------------------
    Resolution: Fixed

Issue resolved by merging pull request 147
            [https://github.com/apache/bookkeeper/pull/147]

            {noformat}
            commit fc4800544bcd60c66fa682e6ffcbf2789b7fbb74
Author:     Matteo Merli <mm...@apache.org>
AuthorDate: Wed May 10 14:15:05 2017 -0700
Commit:     Matteo Merli <mm...@apache.org>
CommitDate: Wed May 10 14:15:05 2017 -0700

    BOOKKEEPER-1059: Upgrade to SLF4J-1.7.25
    
    Author: Matteo Merli <mm...@apache.org>
    
    Reviewers: Enrico Olivelli <None>
    
    Closes #147 from merlimat/slf4j-1.7

            {noformat}
            

> Upgrade to SLF4J-1.7.25
> -----------------------
>
>                 Key: BOOKKEEPER-1059
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1059
>             Project: Bookkeeper
>          Issue Type: Task
>            Reporter: Matteo Merli
>            Assignee: Matteo Merli
>            Priority: Minor
>             Fix For: 4.5.0
>
>
> BookKeeper is currently using SLF4J 1.6.4. By upgrading to 1.7x, the most visible change would be to be able to pass a variable number of arguments without needing to wrap them into a:
> {code:java}
> log.info("msg: {} {} {}", new Object[] {x, y, x});
> // versus
> log.info("msg: {} {} {}", x, y, x);
> {code}
> SLF4J 1.7 has been around since 2012.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)