Re: Resolving to micro version

2018-04-04 Thread Katsuya Tomioka
That explains. I had particularly hard time imagining the clause in the spec. (now I have an example.) Thanks all for help. -Katsuya On Wed, Apr 4, 2018 at 8:20 AM, Neil Bartlett wrote: > Thank you, now the answer is clear. > > You can see that the lower version of rbl-osgi (bundle ID 9) has z

Re: Resolving to micro version

2018-04-04 Thread Neil Bartlett
Thank you, now the answer is clear. You can see that the lower version of rbl-osgi (bundle ID 9) has zero active exports, and it is importing the package com.basistech.rbl.osgi from the higher version of itself. This is because rbl-osgi has both an import and an export of that package. When this h

Re: Resolving to micro version

2018-04-04 Thread Karl Pauls
Can you please share the manifests/headers of the bundles involved with us? regards, Karl On Wed, Apr 4, 2018 at 2:04 PM, Katsuya Tomioka wrote: > Thanks for the explanation. The narrow import range is intentional, I > manually set the import in bnd (via bnd-maven-pugin) to satisfy functional >

Re: Resolving to micro version

2018-04-04 Thread Katsuya Tomioka
Thanks for the explanation. The narrow import range is intentional, I manually set the import in bnd (via bnd-maven-pugin) to satisfy functional requirements; I need to consume the version specifically. The runtime currently happened to have both versions of the component. g! inspect cap osgi.wir