karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benson Margulies <ben...@basistech.com>
Subject Re: <feature> element of a feature
Date Mon, 31 Aug 2015 11:08:21 GMT
So, here's my practical question.

Feature 'A' is made up of many bundles.

Feature 'B' has wiring dependencies on jars in feature 'A', and a few
dependencies that are not part of feature 'A', including transitive

So B has a plain old Maven dependency on the bundle inside 'B' that
has the API, plus its own.

I am trying to work out the POM and feature.xml content so that
feature B's feature.xml shows that it depends on 'A', and that it
lists only those bundles that are not in A.

I've tried a few experiments with feature.xml dependencies, but I end
up with either more or less bundles than I was looking to get.

Is this even a reasonable thing to do, or should I just let feature B
have the redundant bundles?

On Mon, Aug 31, 2015 at 1:30 AM, Jean-Baptiste Onofré <jb@nanthrax.net> wrote:
> name is just the name, you also have the version attribute.
> dependency means that it's a dependency for the resolver, so the resolver
> resolves this feature.
> prerequisite means the feature has to be completely installed before moving
> forward on the current feature installation.
> Regards
> JB
> On 08/31/2015 03:28 AM, Benson Margulies wrote:
>> I'd like to improve the documentation in the feature schema.
>> Could someone elaborate for me on the difference between the
>> 'dependency' and 'prerequisite' attributes of the feature element used
>> to declare a dependency? Since the whole thing is a dependency, why
>> does it have a dependency attribute.
>> Also, am I correct that the 'name' is from the flat namespace, not g/a/v?
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

View raw message