osgi / slf4j-osgi Goto Github PK

Hi,

Are you planning to release this or do you perceive this just as a proof-of-concept? If you are not planning on releasing this, do you have pointers to other resources that try to achieve the same thing (getting SLF4J logging into R7 logging)?

Kind regards,

Jelle

Is the 1.7 branch something we need\want to keep and maintain?

I am wondering if the OSGiServiceProvider should use the basic MDC implementation - BasicMDCAdapter instead of NOPMDCAdapter which is currently used -

Due to the usage of the NOPMDCAdapter, nothing seems to be logged at all.

I want to use this fragment within a RCP application based on Eclipse 4.18. The included equinox runtime seems to implement the osgi log service version 1.5. Since the package import directive for org.osgi.service.log in slf4j.osgi is stated as [1.4,1.5) the fragment fails to resolve in my context. Looking at the source code and the documentation at https://docs.osgi.org/specification/osgi.cmpn/7.0.0/service.log.html#org.osgi.service.log I'm wondering why the version range is so strict.? To my understanding this fragment only consumes the log service api so according to the documentation a version range of [1.4,2.0) should be fine.

Is there a reason this is not available through Maven Central repository? It would be really nice to have it there.

I was looking which bindings available for slf4j integration in Eclipse and stumbled over this repo.
Is there any reason why is this bundle is not added to some Orbit release [1]?

I see there are slf4j bindings available on Orbit like org.slf4j.binding.log4j12, but if I understand it right, this one aims to "simply" route all logs from slf4j to standard Eclipse log (if being added to the Eclipse IDE for example) and that is exactly what was I looking for.

Is this bundle not on Orbit because org.apache.aries.spifly.dynamic.framework.extension is also needed? Or just because no one asked yet?

[1] https://download.eclipse.org/tools/orbit/downloads/drops/R20221123021534/

Currently the Fragment-Host is specified only with slf4j.api it resolves to any version of slf4j (even older ones).
According to semantic versioning it must only resolve to the next release: slf4j.api;bundle-version="[1.7,1.8)" or maybe even more stricter policy when we assume that a logging provider is tightly coupled to the slf4j implementation of slf4j.api;bundle-version="[1.7.25,1.7.26)"