I don't use the deploy folder, but maybe this will help. I have my features as maven artifacts.
<features name=main-features" xmlns="http://karaf.apache.org/xmlns/features/v1.0.0"> <repository>mvn:${groupid}/${artifactid}/xml/features</repository> <feature name="main"> <feature>dependent</feature> </feature> .... </features> http://karaf.apache.org/manual/latest-2.3.x/users-guide/provisioning.html If the dependent feature is not in the current feature, it should be able to find it from a feature repository. On Sep 4, 2013, at 10:59 AM, Mohammad Shadab Ali wrote: > Hi, > > I am facing issue with karaf(2.3.2) features. I have 10 features xml(F1-F10) > placed in the karaf deploy folder. > Feature F2-F10 is dependent upon F1. When I deploy the features one by one in > deploy folder all the features gets installed successfully. > But when I restart karaf, only feature F1 gets installed and rest of the > features are in uninstalled state. Then I manually start the uninstalled > features using features:install command each time. > > Is there any way where I can define the dependency between two features xml. > > Thank you in advance. > > Regards, > Shadab > > > *** This e-mail (and any attachments), is confidential and may be privileged. > It may be read, copied and used only > by intended recipients. Unauthorized access to this e-mail (or attachments) > and disclosure or copying of its > contents or any action taken in reliance on it is unlawful. Unintended > recipients must notify the sender immediately > by e-mail/phone & delete it from their system without making any copies or > disclosing it to a third person.*** > This e-mail (and any attachments), is confidential and may be privileged. It > may be read, copied and used only > by intended recipients. Unauthorized access to this e-mail (or attachments) > and disclosure or copying of its > contents or any action taken in reliance on it is unlawful. Unintended > recipients must notify the sender immediately > by e-mail/phone & delete it from their system without making any copies or > disclosing it to a third person. > >
