To your first question, I suspect you may be looking for the Karaf features Maven plugin:
https://karaf.apache.org/manual/latest-2.2.x/developers-guide/features-maven-plugin.html It permits you to generate features XML directly from a Maven project: https://karaf.apache.org/manual/latest-2.2.x/developers-guide/features-maven-plugin-generate.html This may not get you all the way to a deployable feature, but it should help a good deal. --- A. Soroka Online Library Environment the University of Virginia Library On Jan 10, 2012, at 8:49 AM, scottkm wrote: > Thank you both for your responses, they are very helpful. I do have two > quick follow up questions. > > The first is about the features xml. I see the benefit in having more > control over the deploy artifacts, however when I list a dependency in Maven > it can potentially generate quite a number of dependant Jars (or bundles in > this case). Is there any way to easily generate the features xml file that > would include the bundles that I would require? The current option I see is > to get maven to list all of the dependent Jars, then go through them one by > one to find the URL that I would have to put in the features xml file. I > didn't see any options in the maven-bundle plugin to support this. > > The second question is just about best practices. You mention that you > recommend that new users skip the JBI and use Camel/CXF on ServiceMix > directly. Do you have a link to where this advice, and maybe more, can be > found? > > Thanks again, > Scott > > > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/Feature-repositories-OBR-and-my-own-Jars-tp5131903p5134096.html > Sent from the ServiceMix - User mailing list archive at Nabble.com.
