Felix Meschberger wrote:
> Hi,
>
> Stephan Heuser schrieb:
>> Hi,
>>
>> i am a bit irritated. The manifest of the SCR bundle specifies it
>> needs a version of org.osgi.framework < 2.0.0 . Am i missing
>> something, has the service runtime component merged with the framework
>> bundle?
>
> No merge at all, the SCR bundle just expects a framework as specified in
> R 4.1 or later (but not a 2.0.0 or higher version).

Thanks for your quick answer. Since org.apache.felix.framework 2.0.1
provides version 2.0.1 does this mean declarative services are not
usable with the current stable felix framework bundle?

>From org.apache.felix.framework manifest:

Bundle-Description = This bundle is system specific; it implements
various system services.
Bundle-ManifestVersion = 2
Bundle-Name = System Bundle
Bundle-SymbolicName = org.apache.felix.framework
Bundle-Version = 2.0.1
Export-Package = org.osgi.framework; version="2.0.0", ...

Cheers,
Stephan

>
>> cf. :
>> W/System.err( 1119): org.osgi.framework.BundleException: Unresolved
>> constraint in bundle org.apache.felix.scr [4]: package;
>> (&(package=org.osgi.framework)(version>=1.4.0)(!(version>=2.0.0)))
>
> If I read this correctly, it says that the framework package version
> must be greater than or equal to 1.4 (which is the R 4.1 framework
> package version) and smaller than 2.0.0 (which is a potential future
> framework package version with potentially incompatible changes).
>
> You should check whether the framework you use is recent enough ...
>
> Regards
> Felix
>
>> Cheers,
>> Stephan
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to