[
https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16533166#comment-16533166
]
Björn Kautler commented on LOG4J2-2305:
---------------------------------------
Besides the provided scope that should probably either set in both or in none,
it does not work with 1.8.
It cannot find the class {{org.apache.logging.log4j.spi.AbstractLoggerAdapter}}.
>From a quick skim over your changes, is it correct that you copy over the
>built files from 1.7 and just repackage them for 1.8?
I guess in this case the OSGi manifest entries are not calculated correctly and
thus the bundle does not import the needed packages.
> 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)
