[jboss-jira] [JBoss JIRA] (WFCORE-1620) Upgrade slf4j from version 1.7.7.jbossorg-1 to 1.7.22

Brian Stansberry (JIRA) issues at jboss.org
Wed Feb 1 22:18:00 EST 2017


     [ https://issues.jboss.org/browse/WFCORE-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated WFCORE-1620:
-------------------------------------
    Fix Version/s: 2.2.1.Final


> Upgrade slf4j from version 1.7.7.jbossorg-1 to 1.7.22
> -----------------------------------------------------
>
>                 Key: WFCORE-1620
>                 URL: https://issues.jboss.org/browse/WFCORE-1620
>             Project: WildFly Core
>          Issue Type: Component Upgrade
>          Components: Logging
>            Reporter: James Perkins
>            Assignee: Frank Langelage
>             Fix For: 3.0.0.Alpha18, 2.2.1.Final
>
>
> There should no longer be a need for the forked version. The fix for [SLF4J-167|http://jira.qos.ch/browse/SLF4J-167] should be in version 1.7.14 with some additional fixes for replaying the previously lost logs.
> [Quote from comment on JIRA|http://jira.qos.ch/browse/SLF4J-167?focusedCommentId=17048&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17048]
> {quote}
> The problem of lost logs during initialization in a multi-threaded application is solved by storing and replaying the logs which would be otherwise lost. Fix available in SLF4J version 1.7.15.
> {quote}
> Analysis will need to be done to ensure this works as expected before the fork is no longer required.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jboss-jira mailing list