Re: Predictable order of bundle resolution

Hi Dirk, This is a possibly impractical suggestion in your context, but have you thought about modeling this as services? Something like: Bundle A (ID: 200) - Export-Package: org.foo;version=1.0.0 Bundle B (ID: 210) - Import-Package: org.foo;version="[1.0,2)" - Export-Package:

Re: Enforcing mandatory components for an application

On Wed, 2021-10-13 at 11:17 -0400, Raymond Augé wrote: > I don't think "readiness" is something you completely do inside an > app to > begin with. (assist with? sure!) > > This is why I proposed Condition Service; to model the details > required for > your application to be "ready", hoist that

Re: Enforcing mandatory components for an application

On Tue, 2021-10-12 at 22:59 +0100, Neil Bartlett wrote: > This is an interesting problem and I'm also not clear on why Ray > suggested > the Condition Service as a solution, as I can't see how it helps. > > What you're trying to do is somewhat against the grain in OSGi. We > assume > that the

Predictable order of bundle resolution

Hi, tldr; is the order in which bundles get resolved predictable? We are facing issues with the usage of optional imports. Sometimes an optionally imported package gets wired and sometimes it doesn't. Refreshing the consuming bundle's package imports after startup always works to get the wiring