Re: transitive dependencies of feature descriptors

OK I understand better now. What about changing the scope of the bundle dependency ? Regards JB On Fri, Aug 05, 2016 at 2:34 PM, Benson Margulies < ben...@basistech.com [ben...@basistech.com] > wrote: On Fri, Aug 5, 2016 at 8:32 AM, Jean-Baptiste Onofré < j...@nanthrax.net

Re: transitive dependencies of feature descriptors

I also tend just to let Karaf’s wrap deployer sort out the non-OSGi ones. Works 95% of the time for me. Where the 5% is mostly split packages or where somehow the bundle creator thought it would be a good idea to have an inexplicit dependency, grrrh. Dan. > On 5 Aug 2016, at 13:51, Benson

Re: transitive dependencies of feature descriptors

On Fri, Aug 5, 2016 at 8:41 AM, Daniel McGreal wrote: > Hi, > I tend to prefer setting scope of the dependencies to ‘provided’, either > in the 'aggregator’ or by using dependencyManagement in features. This > means you can stack the features files without having to

Re: transitive dependencies of feature descriptors

Hi, I tend to prefer setting scope of the dependencies to ‘provided’, either in the 'aggregator’ or by using dependencyManagement in features. This means you can stack the features files without having to re-exclude the transitives you’re not interested in. Best, Dan. > On 5 Aug 2016, at

Re: transitive dependencies of feature descriptors

On Fri, Aug 5, 2016 at 8:32 AM, Jean-Baptiste Onofré wrote: > You mean that you use the karaf-maven-plugin to generate the features.xml ? > JB, Yes, I always use the plugin. Regards, benson > > Regards > JB > > On 08/05/2016 02:28 PM, Benson Margulies wrote: > >> JB, >>

Re: transitive dependencies of feature descriptors

You mean that you use the karaf-maven-plugin to generate the features.xml ? Regards JB On 08/05/2016 02:28 PM, Benson Margulies wrote: JB, The jar files incorporated in the uber jar show up in the dependency graph and thus reappear in as 'wrap:' bundles in features. If project X declares a

Re: transitive dependencies of feature descriptors

JB, The jar files incorporated in the uber jar show up in the dependency graph and thus reappear in as 'wrap:' bundles in features. If project X declares a dependency on feature F, then the dependencies of feature F are considered as bundles in project X's feature, because they are part of

Re: transitive dependencies of feature descriptors

Hi Benson, honestly, I don't understand your point ;) You have an "uber" bundle containing packages, and this bundle is in a feature. This feature can be used as an inner feature. So what's the point ? Regards JB On 08/05/2016 02:03 PM, Benson Margulies wrote: Folks, I wonder if someone

transitive dependencies of feature descriptors

Folks, I wonder if someone else has found a way out of this. Consider a project that builds an OSGi bundle by aggregating some non-OSGi jar Maven dependencies. Those dependencies are in the dependency tree of the resulting bundle. Now, consider what happens if you generate a feature to contain