[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534647#comment-16534647 ] Björn Kautler commented on LOG4J2-2305: --- Or with the fragment added that I described as work-around, yes. It would of course be preferable they switch to proper OSGi features like log4j does for finding core. But if they do, it can be adapted in log4j too of course and maybe the artifacts merged again into one. > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534640#comment-16534640 ] Rob Gansevles commented on LOG4J2-2305: --- I have verified is at well that it works, obviously only with the pull-request for slf4j applied. Thanks! > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534601#comment-16534601 ] Björn Kautler commented on LOG4J2-2305: --- Yep, now the 1.8 version works as expected. > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534449#comment-16534449 ] ASF subversion and git services commented on LOG4J2-2305: - Commit 6467586f82ebcfa2bf9174bebe755b0c6ce234c3 in logging-log4j2's branch refs/heads/master from [~ralph.go...@dslextreme.com] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=6467586 ] LOG4J2-2305 - Create separate implementation for SLF4J 1.8 > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534448#comment-16534448 ] ASF subversion and git services commented on LOG4J2-2305: - Commit 0ebbd84d2f2b4e78abb179b9f8313b9cab26fae1 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=0ebbd84 ] LOG4J2-2305 - Create separate implementation for SLF4J 1.8 > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534447#comment-16534447 ] ASF subversion and git services commented on LOG4J2-2305: - Commit 922fefdc7265b110d1a00916630acb786104f2db 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=922fefd ] LOG4J2-2305 - rename module. Add to distribution > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533875#comment-16533875 ] Björn Kautler commented on LOG4J2-2305: --- Ah, ok, then good that I came up with this, as it ever was wrong :-D > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533798#comment-16533798 ] Ralph Goers commented on LOG4J2-2305: - I guess technically it wouldn't conflict with the slf4j-api jar, but it also wouldn't work correctly. The "real" marker factory being used is the one returned by SLF4JServiceProvider. The MarkerFactory it returns is the one Log4jLogger and Log4jMarker need to use. > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[
https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533721#comment-16533721
]
Björn Kautler commented on LOG4J2-2305:
---
Can`t we?
It works for {{log4j-slf4j-impl}} in OSGi, why shouldn't it work for
{{log4j-slf4j18-impl}}?
> 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533717#comment-16533717 ] Ralph Goers commented on LOG4J2-2305: - Thanks. I hadn't noticed that. I guess I have more work to do as we can't be doing 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533705#comment-16533705 ] Björn Kautler commented on LOG4J2-2305: --- Sure it is, `Log4jLogger` and `Log4jMarker` use it. > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533700#comment-16533700 ] Ralph Goers commented on LOG4J2-2305: - I don't understand. StaticMarkerBinder is not allowed to be in an SLF4J 1.8 implementation. JPMS doesn't allow a class in another module's package to be in yours. Furthermore, it isn't referenced by anything. > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[
https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533395#comment-16533395
]
Björn Kautler commented on LOG4J2-2305:
---
> It will take a bit as Jenkins is currently building
No problem, I was asleep anyway, it was getting light outside, so I had to
catch some sleep.
The move seems to have helped (you can see it in the MANIFEST.MF attributes).
But your class reusage is erroneous.
Now errors out because it misses {{org.slf4j.impl.StaticMarkerBinder}} which is
present in the 1.7 but not in th 1.8 artifact.
> 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[
https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533209#comment-16533209
]
Remko Popma commented on LOG4J2-2305:
-
I think it would be better to be consistent:
* {{log4j-slf4j-impl}}
* {{log4j-slf4j18-impl}}
* {{log4j-to-slf4j}}
There is already occasional confusion on the difference between
{{log4j-to-slf4j}} and {{log4j-slf4j-impl}}. Clarity is better than brevity
here IMHO.
> 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533184#comment-16533184 ] Ralph Goers commented on LOG4J2-2305: - 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533183#comment-16533183 ] ASF subversion and git services commented on LOG4J2-2305: - Commit bf5ab8611222efcc606cf944efa93b42e53ff525 in logging-log4j2's branch refs/heads/master from [~ralph.go...@dslextreme.com] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=bf5ab86 ] LOG4J2-2305 - Move dependency unpack before the bundle plugin > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533180#comment-16533180 ] ASF subversion and git services commented on LOG4J2-2305: - Commit af5cd99268cc7e4c2928fb343e23c8113c63594e 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=af5cd99 ] LOG4J2-2305 - Move dependency unpack before the bundle plugin > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533171#comment-16533171 ] Ralph Goers commented on LOG4J2-2305: - Thanks for catching the problem with provided scope. I have fixed that. Yes, I copied the class files because I didn't want two copies with the same names in two different modules. I will try changing the lifecylce phase of when the copying is done and see if that makes a difference. > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533169#comment-16533169 ] ASF subversion and git services commented on LOG4J2-2305: - Commit 2bfb0bae72e0220a7ed60bafcd52e2a3cd3429ab in logging-log4j2's branch refs/heads/master from [~ralph.go...@dslextreme.com] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=2bfb0ba ] LOG4J2-2305 - remove provided scope > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533168#comment-16533168 ] ASF subversion and git services commented on LOG4J2-2305: - Commit 29085717912e54bd7de364b5708d2704001f3832 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=2908571 ] LOG4J2-2305 - remove provided scope > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[
https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533160#comment-16533160 ] Björn Kautler commented on LOG4J2-2305: --- Or rather be provided in both? > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533159#comment-16533159 ] Björn Kautler commented on LOG4J2-2305: --- Shouldn't the `provided` scope be remove again for the 1.7 artifact too? > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533157#comment-16533157 ] Björn Kautler commented on LOG4J2-2305: --- Ah, on https://repository.apache.org/snapshots it is available > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533154#comment-16533154 ] Björn Kautler commented on LOG4J2-2305: --- Well, it makes it clear that it is the implementation of the slf4j api, so that slf4j logging goes to log4j and not the slf4j binding (log4j-to-slf4j) that makes the log4j logging go to slf4j. Of course if you have both names besides each other it should be pretty clear, but on their own it is just a tiny bit clearer and more consistent to the "old" name. But hey, I have no strong feelings about this and in no position to question your decision, just wanted to make you aware if you were not. How often does Jenkins build? Currently your latest changes are not yet in. > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533148#comment-16533148 ] Ralph Goers commented on LOG4J2-2305: - Jenkins should be publishing snapshots to repository.apache.org. I don't think log4j-slf4j-impl has ever been a very popular name so I opted to make it shorter since I don't think there will be any confusion over what it is. That said, if the consensus is to rename it I will do 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533134#comment-16533134 ] Björn Kautler commented on LOG4J2-2305: --- Is there some snapshot builds published somewhere I can verify against or do I need to build them manually locally? Shouldn't `log4j-slf4j18` be called `log4j-slf4j18-impl` for consistency? Otherwise source-wise the commit looks good to me. > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533087#comment-16533087 ] Ralph Goers commented on LOG4J2-2305: - No. I just made the changes against this issue. Please verify. > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533086#comment-16533086 ] ASF subversion and git services commented on LOG4J2-2305: - Commit 70d0e2213d2eac0af2e7866349225b7aa7102ad0 in logging-log4j2's branch refs/heads/master from [~ralph.go...@dslextreme.com] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=70d0e22 ] LOG4J2-2305 - Split SLF4J into 2 modules - one for SLF4J 1.7.x and one for SLF4J 1.8+ > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533085#comment-16533085 ] ASF subversion and git services commented on LOG4J2-2305: - Commit b5ef909bbc12714182f398331b08f225fdacec65 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=b5ef909 ] LOG4J2-2305 - Split SLF4J into 2 modules - one for SLF4J 1.7.x and one for SLF4J 1.8+ > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533028#comment-16533028 ] Björn Kautler commented on LOG4J2-2305: --- Should this be reopened then? Or do you create a new issue to track this, then please provide a link here so I can follow the progress. > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533025#comment-16533025 ] Ralph Goers commented on LOG4J2-2305: - As much as I hate it, I agree that making two different jars is the proper way to handle this. > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[
https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532540#comment-16532540
]
Björn Kautler commented on LOG4J2-2305:
---
[~ralph.go...@dslextreme.com] I'm not sure merging my PR was a good idea.
When {{log4j-slf4j-impl}} depended on 1.8 anyway, 1.8 would have been there and
in its current state needs the service loader mediator to work properly.
Except of course someone excluded slf4j 1.8 and used 1.7 instead.
Now that {{log4j-slf4j-impl}} has slf4j 1.8 only as provided dependency, it is
more likely that one has 1.7 which is the stable version.
For that, the service loader mediator is not necessary, but with my PR, now the
service loader mediator is required to be provided by the consumer, providing
for example {{org.apache.aries.spifly:org.apache.aries.spifly.dynamic.bundle}}
at runtime.
I think you should revert my commit until 1.8 has settled down and it is
finally clear how it has to be done.
If they stay with the Java service loader mechanism for the final release, you
probably need the mediator.
An alternative would be to split {{log4j-slf4j-impl}} into {{log4j-slf4j-impl}}
and {{log4j-slf4j18-impl}}, where only the latter has the service loader
mediator as dependency and the former not, but only the latter would work with
1.8.
> 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530589#comment-16530589 ] Ralph Goers commented on LOG4J2-2305: - [~rgansevles] It has been now. > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530584#comment-16530584 ] ASF subversion and git services commented on LOG4J2-2305: - Commit 0a31a2d2714baf1b4ad97deeb6cacc39ecd6edc7 in logging-log4j2's branch refs/heads/master from [~vampire] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=0a31a2d ] [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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530585#comment-16530585 ] ASF subversion and git services commented on LOG4J2-2305: - Commit 11eba7994fd39f1f3b2c84c254053267657018bb in logging-log4j2's branch refs/heads/master from [~ralph.go...@dslextreme.com] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=11eba79 ] 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530525#comment-16530525 ] ASF GitHub Bot commented on LOG4J2-2305: Github user asfgit closed the pull request at: https://github.com/apache/logging-log4j2/pull/175 > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530524#comment-16530524 ] ASF subversion and git services commented on LOG4J2-2305: - Commit ce2f8cbe6b3a26ea3c023b1437fe2652dada9dd0 in logging-log4j2's branch refs/heads/release-2.x from [~vampire] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=ce2f8cb ] [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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530466#comment-16530466 ] Rob Gansevles commented on LOG4J2-2305: --- I don't see that he pull-request from [~vampire] has been applied. Is the original problem fixed without this change? > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529398#comment-16529398 ] ASF subversion and git services commented on LOG4J2-2305: - Commit a64b7ab0abf62ba60926cc5d0211b7023abc1912 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=a64b7ab ] LOG4J2-2305 - Mark slf4j-api as provided > 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 > > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529397#comment-16529397 ] ASF subversion and git services commented on LOG4J2-2305: - Commit f94b29cf7d1428df6525ec1a4dbd9187294e1a53 in logging-log4j2's branch refs/heads/master from [~ralph.go...@dslextreme.com] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=f94b29c ] LOG4J2-2305 - Mark slf4j-api as provided > 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 > > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529269#comment-16529269 ] Ralph Goers commented on LOG4J2-2305: - The simplest thing might be to mark the slf4j-api dependency as provided. Presumably if you want this then you have SLF4J already. > 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 > > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488685#comment-16488685 ] Björn Kautler commented on LOG4J2-2305: --- Maybe the proper fix for the time being would be to have 1.8 as compile-time only dependency and 1.7 as runtime dependency if this is possible with Maven. > 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 > > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488680#comment-16488680 ] Björn Kautler commented on LOG4J2-2305: --- It does not "say it has support", it depends on it. [http://search.maven.org/remotecontent?filepath=org/apache/logging/log4j/log4j-slf4j-impl/2.11.0/log4j-slf4j-impl-2.11.0.pom:|http://search.maven.org/remotecontent?filepath=org/apache/logging/log4j/log4j-slf4j-impl/2.11.0/log4j-slf4j-impl-2.11.0.pom]1.8.0-alpha2 [https://github.com/apache/logging-log4j2/blob/master/log4j-slf4j-impl/pom.xml#L34] 1.8.0-alpha2 [~ralphgoers] introduced this in [https://github.com/apache/logging-log4j2/commit/a73fce2e726624efdd594f9b23f10ed253ac6884] 8 months ago > 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 > > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480873#comment-16480873 ] ASF GitHub Bot commented on LOG4J2-2305: Github user Vampire commented on the issue: https://github.com/apache/logging-log4j2/pull/175 Of course it would be nicer if the native OSGi service loader mechanism would be supported, but that would need a bit more work I think. (and more experience with OSGi than I have currently) > 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 > > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[ https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480707#comment-16480707 ] ASF GitHub Bot commented on LOG4J2-2305: Github user Vampire commented on the issue: https://github.com/apache/logging-log4j2/pull/175 The failing build is something about not being able to execute Java 7 on Travis, not related to my PR > 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 > > 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)
[jira] [Commented] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
[
https://issues.apache.org/jira/browse/LOG4J2-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480696#comment-16480696
]
Björn Kautler commented on LOG4J2-2305:
---
The problem / difference is, that log4j now depends on slf4j 1.8.
Starting with 1.8 slf4j deprecated the old method to provide an implementation
and replaced it by usage of {{java.util.ServiceLoader}}.
Within OSGi this does not instantly work propery as each bundle is kept in a
separate class loader and thus the service loader mechanism cannot find the
service definition file and thus the service providing the implementation.
For using the new service loader mechanism in OSGi world, you have to utilize
the Service Loader Mediator Specification on both sides.
But thanks to OSGi bundle fragments, you can easily enable the bundles to
properly talk to each other.
You can generate those bundle fragments e. g. via the following two Gradle
tasks as workaround:
{code}
plugins {
id 'osgi'
}
task slf4jApiFragmentJar(type: Jar) {
baseName = project.name + '-slf4jApiFragment'
manifest = osgiManifest {
name = 'net.kautler.test.osgi.slf4j.api.fragment'
symbolicName = 'net.kautler.test.osgi.slf4j.api.fragment'
version = '1.0.0'
classesDir = temporaryDir
classpath = files()
instruction 'Fragment-Host', 'slf4j.api'
instruction 'Require-Capability', '' +
'osgi.extender;' +
'filter:="(osgi.extender=osgi.serviceloader.processor)",' +
'osgi.serviceloader;' +
'filter:="(osgi.serviceloader=org.slf4j.spi.SLF4JServiceProvider)"'
}
}
task log4jSlf4jImplFragmentJar(type: Jar) {
baseName = project.name + '-log4jSlf4jImplFragment'
manifest = osgiManifest {
name = 'net.kautler.test.osgi.log4j.slf4j.impl.fragment'
symbolicName = 'net.kautler.test.osgi.log4j.slf4j.impl.fragment'
version = '1.0.0'
classesDir = temporaryDir
classpath = files()
instruction 'Fragment-Host', 'org.apache.logging.log4j.slf4j-impl'
instruction 'Require-Capability', '' +
'osgi.extender;' +
'filter:="(osgi.extender=osgi.serviceloader.registrar)"'
instruction 'Provide-Capability', '' +
'osgi.serviceloader;' +
'osgi.serviceloader=org.slf4j.spi.SLF4JServiceProvider'
}
}
{code}
PS: Likewise you have to provide fragments for log4j-api and log4j-core to be
able to be properly found and to add a log4j configuration file if not doing
the configuration programmatically.
> 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
>
> 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)
