[jboss-jira] [JBoss JIRA] (WFLY-6775) Upgrade slf4j from version 1.7.7.jbossorg-1 to 1.7.21

James Perkins (JIRA) issues at jboss.org
Fri Jun 24 17:43:00 EDT 2016


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

James Perkins moved WFCORE-1621 to WFLY-6775:
---------------------------------------------

        Project: WildFly  (was: WildFly Core)
            Key: WFLY-6775  (was: WFCORE-1621)
    Component/s: Logging
                     (was: Logging)


> Upgrade slf4j from version 1.7.7.jbossorg-1 to 1.7.21
> -----------------------------------------------------
>
>                 Key: WFLY-6775
>                 URL: https://issues.jboss.org/browse/WFLY-6775
>             Project: WildFly
>          Issue Type: Component Upgrade
>          Components: Logging
>            Reporter: James Perkins
>            Assignee: James Perkins
>
> 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
(v6.4.11#64026)


More information about the jboss-jira mailing list