commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <>
Subject Re: OSGi Version at Package Level
Date Tue, 20 Jun 2017 22:39:28 GMT
On Jun 20, 2017 3:08 PM, "Simon Spero" <> wrote:

On Tue, Jun 20, 2017 at 10:18 AM, Stefan Bodewig <> wrote:

> Interesting. This means OSGi only provides a way for consumers to say
> which version of an API they want, but not which implementation. This
> as a consumer you can't say "I want version 1.19 of Compress because I
> it contains an important fix". This feels more limited in expressiveness
> than I had expected.

Bundles can specify all sorts of Requirements, including implementations,
and bugfix version ranges  (by default, the bugfix component is not
specified in the lower bound, but that is just a default).   It can be a
little too expressive :-)

If a new version becomes available, it can often be swapped in dynamically
(e.g. when using Declarative Services (née Felix SCR)  with Greedy dynamic
reference, an inject  service will be replaced whenever a newer version is

For more on updating and refreshing bundles see:

I do feel that it ought to be possible to have  more aggressive updates for
critical (security) release, though  that's a little orthogonal to the
version range issue.

One day, in a galaxy far far away, we will just be able to push a button to


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message