[
https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16533184#comment-16533184
]
Ralph Goers edited comment on LOG4J2-2305 at 7/5/18 2:21 AM:
-------------------------------------------------------------
The classes are now copied before the bundle plugin runs. I'm not sure how to
check if that fixed the problem but I think it should. Can you verify that? It
will take a bit as Jenkins is currently building and has a second job pending.
The second build is the correct one.
was (Author: [email protected]):
The classes are now copied before the bundle plugin runs. I'm not sure how to
check if that fixed the problem but I think it should. Can you verify that?
> 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)
