[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [orbit-dev] Logback slf4j impl 1.0.3
|
But then why the build failed then? In the manifest of slf4j.api 1.6.1 bundle there is a require capability header. The build fails with error that the slf4j.api 1.6.1 bundle cannot be resolved due to missing required capability.
Currently I excluded logback slf4j 1.0.3 from the build until I find the problem.
-----Original Message-----
From: Gunnar Wagenknecht [mailto:gunnar@xxxxxxxxxxxxxxx]
Sent: Friday, August 24, 2012 11:55 AM
To: Kirchev, Lazar
Cc: orbit-dev@xxxxxxxxxxx
Subject: Re: Logback slf4j impl 1.0.3
Am 24.08.2012 10:10, schrieb Kirchev, Lazar:
> I am trying to add Logback slf4j 1.0.3 (essentially the same as 1.0.0), and I am wondering how version 1.0.0 is added to Orbit without the manifest header Eclipse-GenericCapability: org.slf4j.impl.StaticLoggerBinder; version="a.b.c", which seems to be required in order for the bundle to attach to org.slf4j.api 1.6.1. At least the build fails with such an error, but also in the slf4j.api there is a readme file stating this.
> In version 0.9.27 of logback.slf4j the manifest header is present.
This has been removed because SLF4J 1.6 no longer fails when a binding
is missing (as it did in Indigo/Helios). The part in README is obsolete now.
-Gunnar
--
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx
http://wagenknecht.org/
