It's a know issue.
A possible workaround would be to define the features repo in
etc/org.apache.karaf.features.cfg instead of the features.xml.
I will fix that asap.
Regards
JB
On 03/18/2015 01:09 AM, Aki Yoshida wrote:
I wanted to write a single karaf feature file to do the equivalent of
the following command steps:
feature:repo-add cxf 2.7.15
feature:install cxf
feature:repo-add camel 2.14.2
feature:install camel-cxf
install mvn:temp.com/foo/0.0.1
This will setup my karaf 3.0.3 system with cxf 2.7.15 and camel 2.14.2
to run my foo bundle.
To this using a single feature file, I thought I could write the
following feature file
.
<features ...>
<repository>mvn:org.apache.cxf.karaf/apache-cxf/2.7.15/xml/features</repository>
<repository>mvn:org.apache.camel.karaf/apache-camel/2.14.2/xml/features</repository>
<feature name="my-foo" version="0.0.1" resolver="(obr)">
<feature version="2.7.15">cxf</feature>
<feature version="2.14.2">camel-cxf</feature>
<bundle>mvn:temp.com/foo/0.0.1</bundle>
</feature>
</features>
and just run
feature:install my-foo
However, this didn't work as adding camel-feature repo 2.14.2 in my
feature file is bringing cxf-feature repo 3.0.4. Consequently,
installing my-foo is pulling cxf 3.0.4 instead of cxf 2.7.15.
I tried using <feature version="]2.7,3)">cxf</feature> in my my-foo
feature, but that didn't help either
So I am wondering if there is a simple way to exclude a repo version
referenced in one feature?
Thanks
aki
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
