ok, first of all one issue: your featuresrepository is not completely correct. mvn:org.apache.karaf.assemblies.features/standard/2.2.5/xml/features...
Besides of this you're facing a completely different problem. You're using karaf 2.2.4 and expect it to start 2.2.5 bundles simply because you change the features.xml repository. This wont work that way because of (e.g.; only one reason) etc/startup.properties. It's NOT a good idea to use different karaf features.xml than comming with your karaf distribution (but feel free to change/add any other repository url). I've tested what you've described with karaf 2.2.5 and everything works as expected. Can you pls check if using Karaf 2.2.5 fixes your problems too? Kind regards, Andreas On Thu, Jan 26, 2012 at 09:04, christoforos.vasilatos < christoforos.vasila...@gmail.com> wrote: > So, your suggestion is to create a features.xml and add explicitly the > features that i want to add with their version?Like someone would do in > order to add his own bundles, but use it for i.e. camel cxf etc? > > But isn't it enough to define them in the featuresBoot property of the > org.apache.karaf.features.cfg configuration file (for example > ssh;version=2.2.5,camel;version=2.9.0)? I tried the above and although the > camel and some extra bundles were added correctly at the defined version, > the core packages of karaf were not (for example even though defining > ssh;version=2.2.5 the bundle installed at last was at 2.2.4 version) > > Best Regards, > Christoforos > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/featuresRepositories-is-overriden-by-defined-feature-repositories-tp3688482p3689882.html > Sent from the Karaf - User mailing list archive at Nabble.com. >
