[
https://jira.qos.ch/browse/SLF4J-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19186#comment-19186
]
Björn Kautler commented on SLF4J-412:
-------------------------------------
I don't think that export was corret, as there were no classes in that package
in this bundle.
This export was removed when the OSGi Log Service specification was properly
implemented in 1.7.14.
If you get the missing dependency message, then I suspect it is exactly that,
you have no bundle deployed that provides the OSGi log service.
So either add a bundle that provides the log service or remove this bundle
from your configuration.
For me in my little test project the log service is provided by the bundle
{{org.apache.felix.gogo.command}}.
All the popular OSGi containers should provide an implementation as you can see
at
[https://en.wikipedia.org/wiki/OSGi_Specification_Implementations#101:_Log_Service].
> Missing export in manifest file
> -------------------------------
>
> Key: SLF4J-412
> URL: https://jira.qos.ch/browse/SLF4J-412
> Project: SLF4J
> Issue Type: Bug
> Components: osgi-over-slf4j
> Affects Versions: 1.7.14, 1.7.25
> Reporter: Herve Dumont
> Assignee: SLF4J developers list
>
> Issue is a regression from SLF4J-341.
> version 1.7.13 was exporting org.osgi.service.log
> starting v 1.7.14 org.osgi.service.log is not longer exported,.
> bundle cannot be started due missing dependency org.osgi.service.log.
> Adding
> Export-Package: org.osgi.service.log;uses:="org.osgi.framework";version="1.3"
> should solve the issue
--
This message was sent by Atlassian JIRA
(v7.3.1#73012)
_______________________________________________
slf4j-dev mailing list
[email protected]
http://mailman.qos.ch/mailman/listinfo/slf4j-dev
