Open Hc747 opened 2 years ago
@Hc747 What slf4j are you using?
How is this related to JDK 18? I do not think it is.
Which logging back-end are you using? Is it log4j 2.18 or earlier?
@Hc747 What slf4j are you using?
My configuration is as follows:
Oracle OpenJDK 18.0.2.1+1-1
slf4j_version=2.0.0
log4j2_version=2.18.0
api "org.slf4j:slf4j-api:$slf4j_version"
api "org.apache.logging.log4j:log4j-api:$log4j2_version"
implementation "org.apache.logging.log4j:log4j-slf4j18-impl:$log4j2_version"
implementation "org.apache.logging.log4j:log4j-core:$log4j2_version"
How is this related to JDK 18? I do not think it is.
Which logging back-end are you using? Is it log4j 2.18 or earlier?
Might be related to JDK 18 as the invocation throws an AbstractMethodError
rather than a NoSuchFieldError
- not sure if this behaviour was changed in JDK 18, but it clearly deviates from the expected behaviour, as we arrive in the component of the try-catch clause that catches all exceptions.
I think this issue is related to log4j2 version 2.18.0 which does not yet fully support SLF4J 2.0.
See also LOG4J2-3370
Account for java.lang.AbstractMethodError in same clause of try-catch construct when performing version sanity check.
I.e.