http://bugzilla.slf4j.org/show_bug.cgi?id=75
--- Comment #10 from Ceki Gulcu <lis...@qos.ch> 2009-11-11 09:19:52 ---
Hi Hugues,
Instead of hard-coding the version number of the org.slf4j.impl import
as 1.5.6 to match that exported by logback-classic, I modified the
logback-classic to export the slf4j version it uses by variable name.
Thus, in slf4j-api/src/main/resources/META-INF/MANIFEST.MF we still have
Import-Package: org.slf4j.impl;version=${project.version}
(unchanged)
and in logback-classic/pom.xml for the maven-bundle-plugin we state:
<Export-Package>ch.qos.logback.classic*,
org.slf4j.impl;version=${slf4j.version}</Export-Package>
(instead of hard-coding the value 1.5.6).
This approach is obviously more dynamic. Unless there are unexpected
side-effects of using a lower version for the import than the actual
version of slf4j-api, due to the cyclic nature of slf4j/logback
relationship (per your patch [1] in [2]), we should keep slf4j as is
and modify logback-classic/pom.xml as described above and committed a
few minutes ago. See [3].
[1] http://bugzilla.slf4j.org/attachment.cgi?id=63
[2] http://bugzilla.slf4j.org/show_bug.cgi?id=75
[3]
http://github.com/ceki/logback/commit/4cdca9f671ff8251e7775fee498a7331328ffa5b
--
Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dev mailing list
dev@slf4j.org
http://www.slf4j.org/mailman/listinfo/dev
