Maybe some details could be interesting (I'm pretty sure Morgan removed
the resolver tag without knowing why ;)).
When you use feature namespace 1.3, you use the new feature service. The
feature service embeds a resolver (powered by Felix Resolver). This
resolver can leverage OSGi Repository spec via the resourcesRepositories
config or via <resource-repository/> element in the feature XML. So,
it's no more required to provide a "external" resolver (like OBR).
Anyway, I created a Jira to support the resolver attribute on the
feature element even if we don't use it, just for backward
compatibility. However, I'm a bit mixed there as if the user uses
features namespace 1.3, he should know that resolver attribute is no
more supported.
Regards
JB
On 12/28/2015 02:26 PM, [email protected] wrote:
Hi, and thank you very much for your quick reply!
Indeed I have questions, because I don't really get what you did nor why
it now works :)
- In the feature's pom.xml, you removed the <resolver>(obr)</resolver>
tag. I don't understand why it was there in the first place, I think I
copied it from a tutorial
(http://www.liquid-reality.de/display/liquid/2011/02/15/Karaf+Tutorial+Part+1+-+Installation+and+First+application)
- You also changed the bundle name from "features" to "hello". Was this
necessary or was it just for clarity? Now the name of the bundle, of the
"features" name attribute in the feature.xml file and the "feature"
subelement name attribute in this file are all the same, which one is
used in the assembly pom in the end? I guess the bundle name in the
<dependency> element and the feature (no S) in the <feature> element...
Could I have a hello1 and hello2 features in this feature.xml file?
- You modified the history/dependencies.xml file (or was it
automatically changed by Maven?)
In the end, it seems to me that the only real bug was this obr
resolver... Or did I miss something?
Kind regards,
Ben
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
