[JIRA] Updates for SLF4J-519: Upgrade to 2.0.0-alpha3 from 2.0.0-alpha2 breaks config

SLF4J / SLF4J-519 [Open] Upgrade to 2.0.0-alpha3 from 2.0.0-alpha2 breaks config ============================== Here's what changed in this issue in the last few minutes. This issue has been created There is 1 comment. This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-519 ============================== Issue created ------------------------------ Pelle Krøgholt created this issue on 11/Aug/21 1:17 PM Summary: Upgrade to 2.0.0-alpha3 from 2.0.0-alpha2 breaks config Issue Type: Bug Affects Versions: 2.0.0-alpha3 Assignee: SLF4J developers list Created: 11/Aug/21 1:17 PM Environment: jvm Priority: Major Reporter: Pelle Krøgholt Description: error is logged with: Unexpected problem occured during version sanity checkUnexpected problem occured during version sanity checkReported exception:java.lang.AbstractMethodError: Receiver class ch.qos.logback.classic.spi.LogbackServiceProvider does not define or inherit an implementation of the resolved method 'abstract java.lang.String getRequestedApiVersion()' of interface org.slf4j.spi.SLF4JServiceProvider. at org.slf4j.LoggerFactory.versionSanityCheck(LoggerFactory.java:297)LoggerFactory.java:297 at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:141)LoggerFactory.java:141 at org.slf4j.LoggerFactory.getProvider(LoggerFactory.java:421)LoggerFactory.java:421 at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:407)LoggerFactory.java:407 at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:356)LoggerFactory.java:356 at com.typesafe.scalalogging.StrictLogging.$init$(Logging.scala:23)Logging.scala:23 ============================== 1 comment ------------------------------ Ceki Gülcü on 11/Aug/21 1:24 PM Which version of logback-classic are you using? ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)
participants (1)
-
QOS.CH (JIRA)