By default, the plugin will write all configurations from startup and boot stages. For boot features, it can be further refined using the pidsToExtract parameter on the assembly mojo. For example the default karaf assembly does not extract configs for acls. In all cases, whether the configuration is extract by the FeaturesService at boot stage or not, the bundles should be started after the config is installed.
So the default should be to extract all the cfg files. Guillaume 2017-03-30 17:17 GMT+02:00 CLEMENT Jean-Philippe < [email protected]>: > We build our assembly with the plugin you mentioned. But the assembly > itself, the .tar.gz does not contains the cfg files in the /etc. These > files are populated in the /etc during the first startup. The problem is > that the bundles are also started in parallel during the same time. So > using them may fail. > > Is there an option to force the karaf-maven-plugin to put the cfg files in > the /etc folder inside the .tar.gz archive? > > Regards, > JP > > -----Message d'origine----- > De : Jean-Baptiste Onofré [mailto:[email protected]] > Envoyé : mercredi 29 mars 2017 19:14 > À : [email protected] > Objet : Re: KARAF-4829 Make sure configFile in features makes config > available early > > Hi JP, > > yes, you can create your custom distribution with resource: the > karaf-maven-plugin will include it in the final archive. > > Regards > JB > > On 03/29/2017 07:02 PM, CLEMENT Jean-Philippe wrote: > > Hi, > > > > About the issue KARAF-4829 about config files which may be available > after bundles start, I'm looking for a workaround. > > > > Is there a way to force cfg files to be copied to /etc during assembly? > > > > Thanks! > > > > Regards, > > JP > > > > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com > -- ------------------------ Guillaume Nodet
