Re: exported package in bundle A is not able to be imported in bundle B

2016-03-29 Thread asookazian2
I am seeing "Activator start error" when doing a feature:install xxx. What is recommended course of action? Just install the bundles one by one, in the top to bottom order from the features xml? Seems difficult to debug this way... -- View this message in context:

Re: exported package in bundle A is not able to be imported in bundle B

2016-03-29 Thread Tim Ward
Using an Activator minimises your module's dependencies, but at the expense of getting any help in this sort of situation. It's also really easy to make mistakes when doing it, and hard to get useful integration with things like configuration admin. I would always recommend that an application

Re: exported package in bundle A is not able to be imported in bundle B

2016-03-29 Thread Tim Ward
The error that you've provided indicates a missing service dependency for a service exposing the com.foo.bar.myClass interface. You should investigate why this service is not present, or if it is, why bundle B has not wired to the same class space for package com.foo.bar as the service

exported package in bundle A is not able to be imported in bundle B

2016-03-28 Thread asookazian2
Karaf 3.0.3 bundle B is in GracePeriod (and ultimately Failure) with dependency on bundle A (which is active and has lower start-level than bundle B). eventually bundle:diag 123 (for bundle B) gives: Status: Failure Blueprint 3/28/16 3:24 PM Exception: null