We are not fully compatible with this version of SLF4J. It had some initialization race conditions so Substitute Loggers were invented. Anyway, there is a new interface we need to implement.
Ralph Begin forwarded message: > From: "Remko Popma (JIRA)" <[email protected]> > Date: April 23, 2016 at 4:13:12 AM MST > To: [email protected] > Subject: [jira] [Closed] (LOG4J2-1375) Update SLF4J from 1.7.13 to 1.7.21 > Reply-To: "Log4J Developers List" <[email protected]> > > > [ > https://issues.apache.org/jira/browse/LOG4J2-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Remko Popma closed LOG4J2-1375. > ------------------------------- > Resolution: Fixed > >> Update SLF4J from 1.7.13 to 1.7.21 >> ---------------------------------- >> >> Key: LOG4J2-1375 >> URL: https://issues.apache.org/jira/browse/LOG4J2-1375 >> Project: Log4j 2 >> Issue Type: Improvement >> Components: SLF4J Bridge >> Affects Versions: 2.5 >> Reporter: Remko Popma >> Assignee: Remko Popma >> Fix For: 2.6 >> >> >> Update SLF4J from 1.7.13 to 1.7.21 > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
