Hi Aki, could you open an issue for the "miss-documentation" :)
for your question, no this isn't possible as the version is in the bundle maven coordinate. But if you have a OBR resolver and enable the OBR resolving this should help already with installing new bundles where the requirements are just in the manifest. regards, Achim 2015-06-09 10:59 GMT+02:00 Aki Yoshida <[email protected]>: > First I start with the document part: > The below description is not really correct and I think it should be > corrected somehow. > > https://karaf.apache.org/manual/latest/users-guide/provisioning.html#Dependentfeatures > > ========== > ... > It's possible to define a version range for a dependent feature: > > <feature name="spring-dm"> > <feature version="[2.5.6,4)">spring</feature> > ... > </feature> > > The feature with the highest version available in the range will be > installed. > =========== > > Should it be saying something like the following? > If the feature within the specified version range has not been > installed, the one with the highest version available in that range > will be installed. > > And now the feature question part: > The reason why I looked up the above document was that I was looking > for a way to do something similar for bundles. So, one might say: > > <feature name="foo"> > <bundle version="[1.2,3)">mvn:com.me/foo-core/2.1</bundle> > > to indicate the bundle with the specified version will be installed if > this bundle within the specified version range has not been previously > installed. > > regards, aki > -- Apache Member Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> Software Architect / Project Manager / Scrum Master
