> Steinar Bang :
> Jean-Baptiste Onofré :
>> no, there's not yet this function in Cave. However, it could be
>> interesting. As, I'm planning to resume work on Cave in the coming
>> weeks, so, it's something I can deal with.
> Great to hear! I'll be happy to be the betatester (or even alp
Hi Kevin,
> I was not aware the framework could not wire the package when resolving the
> bundle even if the package is present and exported.
This is true only for optional imports and can occur if the exported package
has an incompatible version, or if a uses constraint prevents the class spac
> Jean-Baptiste Onofré :
> no, there's not yet this function in Cave. However, it could be
> interesting. As, I'm planning to resume work on Cave in the coming
> weeks, so, it's something I can deal with.
Great to hear! I'll be happy to be the betatester (or even alpha-tester)
of this feature
Hi Steinar,
no, there's not yet this function in Cave. However, it could be interesting. As,
I'm planning to resume work on Cave in the coming weeks, so, it's something I
can deal with.
Regards
JB
On 09/04/2017 05:46 PM, Steinar Bang wrote:
Is there functionality in Karaf Cave that can be u
Is there functionality in Karaf Cave that can be used to watch a remote
repos for snapshot updates of bundles?
Ie. use karaf cave to achieve functionality that is similar to what can
be done on a local repository using "bundle:watch *"?
Thanks!
- Steinar
Tim,
Thanks for the catch. I'm dealing with some third party libs that aren't
OSGi bundles and having to do stuff with declaring things optional and this
one slipped into the mix.
I was not aware the framework could not wire the package when resolving the
bundle even if the package is present an
Hi Kevin,
This problem occurs because you have incorrectly marked the import for the
“com.foo.interfaces” package as “resolution:=optional”. This package is *not*
optional as a type from it is is injected into your blueprint bean which in
turn means that the type must be loadable for your bundl
