Alternatively, I've tried to define the repo / feature to be started at boot time, by editing org.apache.karaf.features.cfg. But that didn't seem to help.
? ---------- Forwarded message ---------- From: Ed Hillmann <[email protected]> Date: Thu, Jul 2, 2015 at 1:58 PM Subject: In 4.0.0, can my features.xml install another repository? To: [email protected] Hi. I have a features.xml that defined my bundles. My bundles in turn use code provided from the apache-cxf project. To date, in order to set up my karaf instance, I have - At the console, used feature:repo-add to add the cxf repository ("repo-add cxf") - At the console, used feature:repo-add to add my own features.xml from a mvn address - At the console, used feature:install to install my bundles. In my bundles, I have listed <feature version="3.1.0">cxf</feature> This all works. However, I was hoping I could skip the first step. So, instead of manually installing the cxf repo, have it defined as part of my features.xml. It looks like it is possible, at the schema supports it. So, at the head of my features file, it looks like this... <features name="${project.artifactId}-${project.version}" xmlns=" http://karaf.apache.org/xmlns/features/v1.3.0";> <repository>mvn:org.apache.cxf.karaf/apache-cxf/3.1.0/xml/features</repository> The hope was that now I could just repo-add my own features.xml file, and the act of installing my feature would in turn add the cxf repo. But, that's not happening. When I attempt to feature:install my bundles (which depend on cxf), I get this error: Error executing command: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=cxf; type=karaf.feature; version=3.1.0 I dare say that, if I manually add the cxf repo, this will then work fine. Should this work? If so, am I doing something wrong? Is there another command I should be running? Thanks for any help, Ed
