Hi, Generating automatically a feature is basic approach.
Using this approach, you can use a template file if you want to use more complex features set. FYI, in Karaf, we don't generate the features XML (only the standard one with template): we write all features XML by hand to have fully control and leverage all features flavors. Regards JB On Mon, Aug 8, 2022 at 1:40 PM Richard Hierlmeier <[email protected]> wrote: > > I have the same problem. I define feature dependencies in > > src/main/feature/features.xml > > For each feature dependency I have to define in the pom a version or version > range property. > > Example: > https://github.com/rhierlmeier/vaadin8_karaf_demo/blob/main/src/main/feature/feature.xml > > You can find the configuration of the karaf maven plugin here: > https://github.com/rhierlmeier/vaadin8_karaf_demo/blob/main/pom.xml > > This approach works, but is has the following disadvantages: > > * You can not reuse feature version or version range properties with the > Maven BOM mechanism (import the dependency management). > * CI-system like Jenkins track build dependencies via Maven dependencies. > Jenkins will not trigger a build of a project when the parent feature changes. > > Regards > > Richard > > > > > > > > > > > > > Am Mo., 8. Aug. 2022 um 11:49 Uhr schrieb Ephemeris Lappis > <[email protected]>: >> >> Hello. >> >> I can't find any way to add dependent features to the feature I try to >> generate using the maven plugin. >> >> The maven dependencies are added as expected with the matching bundles. >> >> How can I add features ? I've tried putting a feature.xml file in the >> src/main/feature folder, but then the generation just copy this file >> and do not update it... >> >> Thanks for your help. >> >> Regards.
