[slf4j-dev] [JIRA] (SLF4J-470) slf4j upgrade from 1.5.6 to 1.7.28 is causing default logging level to DEBUG

[QOS.CH (JIRA)]

    [ https://jira.qos.ch/browse/SLF4J-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19956#comment-19956 ] 

Shankar U H commented on SLF4J-470:
-----------------------------------

We were using logback-classic 1.1.3 with slf4j 1.5.6 then upgraded logback-classic to 1.2.3 and slf4j to 1.7.8

> slf4j upgrade from 1.5.6 to 1.7.28 is causing default logging level to DEBUG
> ----------------------------------------------------------------------------
>
>                 Key: SLF4J-470
>                 URL: https://jira.qos.ch/browse/SLF4J-470
>             Project: SLF4J
>          Issue Type: Bug
>          Components: Core API
>    Affects Versions: 1.7.28
>            Reporter: Shankar U H
>            Assignee: SLF4J developers list
>
> Hi team,
> Recently we had to upgrade logback-classic and as its dependency we upgraded slf4j-api from 1.5.6 to 1.7.28.
> After this upgrade,we are seeing DEBUG logs being set by default.
> Reverting back to 1.5.6 does not have this problem.
> No configuration changes were done ,just the jar was replaced with latest jar.
>  
> Please let us know how we can have same log behaviour as in slf4j-api 1.5.6 with slf4j-1.7.28 without any configuration changes.



--
This message was sent by Atlassian JIRA
(v7.3.1#73012)