[LOG4J2-3545] Log4J-JCL should have the same OSGI configuration as Log4j-SLF4J18

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.17.2
• Fix Version/s: 2.19.0
• Component/s: JCL Bridge
• Assignee: Piotr Karwasz
• Reporter: Johan Compagner
• Created: 28/Jun/22 13:18
• Updated: 09/Sep/22 19:19
• Resolved: 08/Sep/22 03:58

Description

if you look at the manifest in this jar:

https://repo1.maven.org/maven2/org/apache/logging/log4j/log4j-jcl/2.17.2/log4j-jcl-2.17.2.jar

compared to the one that is in here:

https://repo1.maven.org/maven2/org/apache/logging/log4j/log4j-slf4j18-impl/2.17.2/log4j-slf4j18-impl-2.17.2.jar

 

then slf4j has the right OSGI manifest entries to work correctly with the ServiceLoader

SLF4j has:

 

Require-Capability: osgi.extender;filter:="(osgi.extender=osgi.service
 loader.registrar)",osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.8))"
Provide-Capability: osgi.serviceloader;osgi.serviceloader="org.slf4j.s
 pi.SLF4JServiceProvider"

 

JCL has:

 

Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.8))"

 

this should become to fully support it in an OSGi environment:

 

Require-Capability:  osgi.extender;filter:="(osgi.extender=osgi.servicelo
 ader.registrar)",osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.8))"
Provide-Capability: osgi.serviceloader;osgi.serviceloader="org.apache.commons.logging.LogFactory"

 

to follow the spec: 133 Service Loader Mediator Specification - OSGi Enterprise 7