Hi Nicolas The purpose of boot features is to start in early stage, so it uses the cfg file as definition.
In your case, you should use inner and prerequisite feature. Do you have some dependencies between kar ? Why don't you use directly feature instead of packaging as a kar ? Can you explain exactly what you are trying to do ? Karaf always store the feature state (in the resolver), so, if you first install kar1, then kar2, when you restart, the resolver will reinstall/start those features. So, you don't have to use a boot feature: if you don't remove the data folder, the installed features and repositories are stored. Regards JB On 05/07/2018 13:52, Nicolas Brasey wrote: > Hi all, > > I'm trying to find out if there is way to install a feature and make it > as a boot feature without manually altering the feature cfg file > (org.apache.karaf.features.cfg). Checking in karaf's code seems to > indicate there is no way to do this programmatically. > > Ideally, it would be a flag in the feature:install command to indicate > to add this feature as a boot feature. > > The reason we need this is that our solution is an integrated solution > which is delivered by different departments: > > 1) Product 1 (kar 1) => dev team A > 2) Product 2 (kar 2) => dev team B > 3) Integration layer (camel routes essentially) (kar 3) => integration team > > All these different teams delivering a self contained kar file with a > feature which should be installed and started when karaf starts in order > to have the global solution running. > > We are using karaf v.4.1.2 which does not seems to persist which > features have been installed (only the boot features). I'm not sure > about the v.4.2.x... > > I know Karaf since not so long, but I believe Karaf has been designed so > that the delivery team is supposed to create a Karaf distribution and > assembling the required boot features at build time. If this is true, > then it is not ideal according to how our internal process is made. > > Any thoughts? > Thanks! > > Best regards, > Nicolas > > > > > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
