Hello. I have some Karaf features based on the same template, using a secondary feature to set a configuration file. Something like that :
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <features xmlns="http://karaf.apache.org/xmlns/features/v1.6.0"; name="my-test"> <feature name="my-test-cfg" description="TEST::CFG" version="1.0.0.SNAPSHOT"> <details>TEST :: Configuration</details> <configfile finalname="etc/alice_esb_bbbmmm999_f902.cfg" override="true"> mvn:info.my-testing/my-test/1.0.0-SNAPSHOT/cfg/configuration </configfile> </feature> <feature name="my-test" description="TEST" version="1.0.0.SNAPSHOT"> <details>TEST</details> <feature prerequisite="true">test-support</feature> <feature version="1.0.0-SNAPSHOT" prerequisite="true">my-test-cfg</feature> <bundle>mvn:info.my-testing/my-test/1.0.0-SNAPSHOT</bundle> </feature> </features> When I add my repo and then install the main feature, the first time the configuration file seems to be installed after the feature and its bundle starts and fails because properties are mlissing. This seems to be a random behavior : sometimes, it works. What can I do to ensure the config. file is installed and "visible" always before the bundle starts ? Is this an issue ??? I have the same behavior on version 4.4.1 and 4.4.3. Thanks for your help. Regards.
