>>>>> Kerry <[email protected]>: > Yes that is what I meant, I have to use a template to create a > features.xml. I've looked at the code for GenerateDescriptorMojo and > searched the Karaf source for an example of what I need but couldn't > find anything.
I've created a feature request for this: https://issues.apache.org/jira/browse/KARAF-5512 > Using the template technique I've also discovered that when I deployed > my feature it can fail. For example if I have 3 of my bundles A, B and > C in the feature such that: > B depends on a service from C and A depends on B > deployment can fail due to a required service from C not being > available 'in-time' for B - I think that's what happening. If I deploy > the bundles individually everything works. I'll try playing around > with it but this is obviously nothing to do with the > GenerateDescriptorMojo. Hm... B should be robust enough to handle services arriving at any time and in any order. But if bundle B is outside of your control, then maybe you could force the correct load order in some way...? Maybe a hiearchy of feature dependencies would do the trick? Ie. make a feature for C that loads C. Then make a feature for B that loads bundle B and requires feature C. Then make a feature for A that loads bundle A and requires feature B. Then make your feature be dependent on feature A. Something like that...?
