Which version of org.apache.logging.log4j.log4j-slf4j2-impl supports org.slf4j.slf4j-api version 2.0.0 or more #2475
-
We are mandated to upgrade org.slf4j.slf4j-api to version greater than 2.0.0 but when we upgrade it OSGI framework complaints that current version (2.17.1) of org.apache.logging.log4j.log4j-slf4j2-impl supports SLF4J version greater than equal to 1.7.0 and less than equal to 2.0.0 We checked all the versions of org.apache.logging.log4j.log4j-slf4j2-impl till Beta 3 but none of them supports SLF4J version greater than 2.0.0 Can you please help if their is a plan to release a supported version or any workaround? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
You are probably talking about the SLF4J 2.x does not bring any major (i.e. breaking) changes to the public API, but it has breaking changes for providers, therefore we had to introduce a new artifact BTW: I see that from a user perspective having two variants of the same SLF4J-to-Log4j API bridge is confusing. Would it help if we deprecate |
Beta Was this translation helpful? Give feedback.
@bbhansali1,
You are probably talking about the
log4j-slf4j-impl
artifact (bundle symbolic nameorg.apache.logging.log4j.slf4j-impl
before version 2.21.0 andorg.apache.logging.log4j.slf4j.impl
since then). That artifact will only support SLF4J 1.x.SLF4J 2.x does not bring any major (i.e. breaking) changes to the public API, but it has breaking changes for providers, therefore we had to introduce a new artifact
log4j-slf4j2-impl
to support it. That is the artifact that you want to use.BTW: I see that from a user perspective having two variants of the same SLF4J-to-Log4j API bridge is confusing. Would it help if we deprecate
log4j-slf4j-impl
and remove it from the distribution in the nex…