Ramesh created SLF4J-441:
----------------------------
Summary: XLogger exit() method is not backward compatible after we
update SLF4J API to 1.7.25
Key: SLF4J-441
URL: https://jira.qos.ch/browse/SLF4J-441
Project: SLF4J
Issue Type: Bug
Components: Core API
Affects Versions: 1.7.25
Environment: JDK 1.8
Maven Eclipse Jetty plugin 9.4.8.v20180619
SLF4J API - 1.7.25
SLF4J EXT - 1.7.25
Reporter: Ramesh
Assignee: SLF4J developers list
Our code has the below code in different places with different version of
exit() method.
LOGGER.exit()
LOGGER.exit(Object)
LOGGER.exit(booleanValue)
We are currently using SLF4J API 1.7.2 and now we are trying to update to SLF4J
1.7.25 to address one security vulnerability issue. During update, we are
seeing this exception
{color:#ff0000}Caused by: java.lang.NoSuchMethodError:
org.slf4j.ext.XLogger.exit(Ljava/lang/Object;)V{color}
{color:#ff0000}{color:#333333}Seems XLogger exit() method is enhanced in 1.7.6
and see the method signature is changed from{color}
public void exit(Object result) \{{color}
{color:#ff0000}}{color}
{color:#ff0000}{color:#333333}to{color} {color}
{color:#ff0000}public <T> T exit(T result) \{{color}
{color:#ff0000}}{color}
{color:#333333}I think this change is not backward compatible and we could not
able to update the SLF4J version.{color}
{color:#333333}Is it possible to make the change backward compatible? Or Please
suggest how we can overcome the exception during update?{color}
--
This message was sent by Atlassian JIRA
(v7.3.1#73012)
_______________________________________________
slf4j-dev mailing list
slf4j-dev@qos.ch
http://mailman.qos.ch/mailman/listinfo/slf4j-dev
