Hello. You're right, dependencies in scope "provided" are ignored (not included as bundles), useful for dependencies that are needed at build time, but are provided by features. Dependencies in scope "compile" (default), are included as expected when the plugin works. For me it works now in two cases : 1) with packaging "bundle", including the artifact itself (and also a configuration file to be deployed to etc) => this feature is for deploying applicative modules with their dependencies 2) with packaging "pom" (no artifact to build) => this feature aims to provide all our OSGi services implementations that applicative modules use via their API and references.
The only case that doesn't work is using the packaging "feature" :( ! Thanks a lot for your help. Regards. Le mar. 9 août 2022 à 12:55, Steinar Bang <[email protected]> a écrit : > > >>>>> Ephemeris Lappis <[email protected]>: > > > Hello. > > I've tried using such a template, and all the elements from it are > > used, with filtering to generate the result file, but maven > > dependencies are not added as bundles to my feature. > > > It seems that using the template makes the plugin ignore bundles > > dependencies. > > If the bundle dependencies have <scope>compile</scope> they will be > included in the filtered feature templace (at least they are, for me). > > But if they have <scope>provided</scope> they will not be added. >
