You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2019/03/23 21:39:00 UTC

[jira] [Commented] (LOG4J2-2573) Update Slf4j from 1.7.25 to 1.7.26

    [ https://issues.apache.org/jira/browse/LOG4J2-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16799813#comment-16799813 ] 

Ralph Goers commented on LOG4J2-2573:
-------------------------------------

This is not a problem. There is no reason for Log4j to upgrade to SLF4J 1.7.26 as that is not the minimum version of SLF4J we support. Our code tolerates the EventData class being missing at runtime so users can use 1.7.26 without problems.

> Update Slf4j from 1.7.25 to 1.7.26
> ----------------------------------
>
>                 Key: LOG4J2-2573
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2573
>             Project: Log4j 2
>          Issue Type: Improvement
>            Reporter: Gary Gregory
>            Priority: Major
>
> Update Slf4j from 1.7.25 to 1.7.26.
> Slf4j breaks compatibility (again) by no longer providing {{org.slf4j.ext.EventData}} in slf4j-ext.
> Our class {{org.apache.logging.slf4j.EventDataConverter}} refers {{org.slf4j.ext.EventData}}.



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