I am not sure what "install mode” is. I want some of the bundles to automatically start, but not others.
I am not sure it is a bug, most likely it is my poor understanding of how the features.xml and the karaf-maven-plugin work. In case it helps, I’ll try to explain my scenario better: I have two features, feature A and feature B. Feature B depends on feature A. In the karaf-maven-plugin configuration I added both features A and B under the bootFeatures section. The issue is that I don’t want some of the feature from A to start but they do, even when I added the <bundle start="false”> to these features in the feature A features.xml declaration. Maybe there is another way to do this? I saw some blacklistedBundles configuration the karaf-maven-plugin but I am not sure what it does. Thanks and best regards, Alex soto > On Feb 4, 2016, at 11:12 AM, Jean-Baptiste Onofré <[email protected]> wrote: > > Hi Alex, > > I guess that when you do feature:install, the bundle is started anyway. > > Do you define the install mode at feature level ? Or you want to start some > bundles but not all, correct ? > > AFAIR, we have a Jira about that. Let me check. > > Regards > JB > > On 02/04/2016 05:08 PM, Alex Soto wrote: >> Hello, >> >> I have a features.xml in which I don’t want to auto start some of the >> bundles. So I use this declaration: >> >> <bundlestart="false”> >> >> Yet, it does not appear to do what I expect, as the feature still tries >> to start. I should mention that I am using a custom distribution using >> the "karaf-maven-plugin” where this feature is added either to the >> <bootFeatures> or <installedFeatures> with the same result. >> >> I am using Karaf version 4.0.3. >> >> Best regards, >> Alex soto >> >> >> > > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com
