[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16530586#comment-16530586 ]
ASF subversion and git services commented on LOG4J2-2305: --------------------------------------------------------- Commit 76a7b182424e6e6eba255cd8cb34f0166414c823 in logging-log4j2's branch refs/heads/release-2.x from [~ralph.go...@dslextreme.com] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=76a7b18 ] LOG4J2-2305 - Make java.util.ServiceLoader properly work in OSGi by using the Service Loader Mediator Specification > Log4j 2.10+not working with SLF4J 1.8 in OSGI environment > --------------------------------------------------------- > > Key: LOG4J2-2305 > URL: https://issues.apache.org/jira/browse/LOG4J2-2305 > Project: Log4j 2 > Issue Type: Bug > Affects Versions: 2.10.0, 2.11.0 > Reporter: Rob Gansevles > Priority: Major > Fix For: 2.11.1 > > > I have a simple osgi plugin that just logs something to slf4j Logger in the > Activator's bundle start method. > When I install and start log4j-core-2.11.0.jar, log4j-api-2.11.0.jar, > log4j-slf4j-impl-2.11.0.jar and slf4j-api-1.8.0-beta1.jar in a clean felix > gogo shell, and then install and start my plugin, it prints the > No-SLF4J-providers-were-found message. > > > It does work if I do the same with log4j 2.9.1 and slf4j-api-1.7.25. > > You can find my simple plugin on github: > [https://github.com/rgansevles/osgi-slf4j-sample] > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)