Exactly, you are in the case where stage can help ;) Regards JB
> Le 13 sept. 2021 à 18:06, Stefan Günst <[email protected]> a écrit : > > Hi JB, > > so the strict order of features guarantees that (in sync mode the default). > That is how we do it at the moment. > > But: we got situation sometimes on slow systems clean start where we start > feature „war“ and than later the webapp that needed this but got error > unknown protocol „war“ … > > Regards > > Stefan > > > > >> Am 13.09.2021 um 17:50 schrieb Jean-Baptiste Onofré <[email protected]>: >> >> Hi Stefan, >> >> I guess you mean stage in boot features. >> >> The use case is when you have boot features that requires another boot >> features to start or a specific order. >> >> The stage allows you to "force" the installation of some features before >> others. >> >> featuresBoot=(A,B),C,D >> >> We are "sure" that A and B are completely installed before installing C and >> D features. >> >> Classic example is wrap: if you need wrap in your feature, you have to >> install wrap before your feature, so you put wrap in the first stage. >> >> Regards >> JB >> >> On 13/09/2021 17:24, Stefan Günst wrote: >>> Hi JB, >>> thank you very much! >>> >>>> The same applies with stage: >>> That is very interesting and i think we dont know the possibility! >>> Can you give us a hint/link how to control this in a real scenario? >>> Regards >>> Stefan >>>> Am 13.09.2021 um 14:07 schrieb Jean-Baptiste Onofré <[email protected]>: >>>> >>>> Hi Stefan, >>>> >>>> sorry, I missed your message. >>>> >>>> By default, the boot features are started in sequence (sync) meaning: >>>> >>>> featuresBoot=A,B,C >>>> >>>> means first A will be installed, and then, once A is completely installed, >>>> B will be installed, etc >>>> >>>> The same applies with stage: >>>> >>>> featuresBoot=(A,C),B >>>> >>>> so, A will be installed then C, then once A and C are fully installed, B >>>> will be installed. >>>> >>>> In async mode, A,B,C will be installed in parallel and the resolver will >>>> try to find the optimal order. >>>> The purpose is to speed up the startup but it's "less" predictable. >>>> >>>> Regards >>>> JB >>>> >>>> On 31/08/2021 16:00, Stefan Günst wrote: >>>>> Hi, >>>>> no one can comment ? >>>>>> Am 18.08.2021 um 17:19 schrieb Stefan Günst <[email protected]>: >>>>>> >>>>>> Hello, >>>>>> >>>>>> can anyone explain what this is for/what it does and why it is default = >>>>>> false. >>>>>> We have situations where it helps to start our distribution without any >>>>>> errors if we set this to „true“ in org.apache.karaf.features.cfg >>>>>> >>>>>> Any risk to set it to true? >>>>>> >>>>>> >>>>>> >>>>>> Stefan >>>>>> >>>>>> >>>>>> >>>>>> >
