That's not entirely true. The featuresBoot ordering has been fixed by karaf-4642.
On Fri, Aug 26, 2016 at 3:42 AM Guillaume Nodet <[email protected]> wrote: > The only way to influence the start order of bundles is to specify the > start level on the feature or on the feature's bundles using the > start-level attribute (see > https://github.com/apache/karaf/blob/karaf-4.0.x/assemblies/features/standard/src/main/feature/feature.xml > for some examples). > > In Karaf 4.x, the features are resolved and installed in a single pass, so > the order is lost. > > 2016-08-26 4:58 GMT+02:00 oski_bear <[email protected]>: > >> Hello, I'm a long-time user of Karaf 2.4.0 trying to migrate my >> application >> to Karaf 4.0.5. One thing I've noticed is that in this new version of >> Karaf >> there doesn't seem to be any way to specify the order in which bundles are >> ordered. >> >> For example, if I specify "bootFeatures" in the karaf-maven-plugin they >> don't start in the order that I list them. Additionally, when I create my >> own features they don't load in the order they are written and the >> container >> does not seem to respect the start levels. >> >> Am I missing something here? Is there a way to enforce a certain order in >> the boot features with the karaf-maven-plugin? Is there a way to force an >> order when defining a feature? >> >> Please help me understand. >> >> >> >> -- >> View this message in context: >> http://karaf.922171.n3.nabble.com/Karaf-4-0-5-bundle-startup-order-tp4047689.html >> Sent from the Karaf - User mailing list archive at Nabble.com. >> > > > > -- > ------------------------ > Guillaume Nodet > ------------------------ > Red Hat, Open Source Integration > > Email: [email protected] > Web: http://fusesource.com > Blog: http://gnodet.blogspot.com/ > >
