The karaf OBR commands should not be used, only the feature:xxx ones. You don't have to wrap your requirements into anything, you don't even have to write a feature if you don't need. Any kind of requirements can be added to the karaf deployer using :
feature:requirement-add 'requirement:osgi.identity;osgi.identity=org.apache. aries.blueprint.core;type=osgi.bundle;version="[1,2)"' The only prerequisite is to add the needed xml repository into etc/org.apache.karaf.features.cfg using the following syntax: resourceRepositories = \ xml:url-to-xml-repository and restart the features-core bundle after the modification so that it's taken into account. 2015-11-26 15:55 GMT+01:00 Christian Schneider <ch...@die-schneider.net>: > After discussing some of the ideas with Peter Kriens and JB I think the > application bundles you mentioned could be a great asset. > You could just create a bundle that represents your top level requirements > like you maybe already do. > > Then you could use the karaf obr commands to install your obr index and > install the application bundle. That might already work out of the box. > > Christian > > On 26.11.2015 14:40, Christian Schneider wrote: > > We are currently discussing this on the karaf irc. > As the long term solutions are not yet ready I would use a practical > approach for now. > > How about creating a feature with a list of bundles out of the -runbundles > that bndtools creates? > That would then not even require a repository. > > Christian > > > -- > Christian Schneiderhttp://www.liquid-reality.de > > Open Source Architecthttp://www.talend.com > >