Hi Clause, thanks for summing up what we talked of on IRC :)
I think it could be even easier. We could add a bundle tracker for features.xml files that will install those with the features service. For this we don't even need a special syntax of the osgi:install url (and actually if you want a url-handler to take control of it you need osgi:install features:mvn:xxxx) Something like the web-extender of pax-web could be done, and should be quite easy. regards, Achim 2013/1/18 Claus Ibsen <claus.ib...@gmail.com> > Hi > > So when people get started with Apache Karaf and Camel (eg not going > down the full ESB with SMX) then I would like to make that much > easier. > For example to tell them how easy you can install some of the examples > we provided with Apache Camel > http://camel.apache.org/examples > > Many of these examples have been prepared for OSGi and have embedded > features.xml file, so in theory they are ready to install. > > Though I could not find a way to install the example in Karaf without pain. > > eg I want to do > > cd apache-karaf-2.3.0 > bin/karaf > > features:choose camel 2.11.0 > > // and how to install my example, such as camel-example-sql > ????? > > > The camel features does not contain examples. > And frankly I would like Karaf to be able to install a bundle but use > the features.xml file that is included in the JAR in the root > classpath. (Or some other directory if Karaf has a standard for that). > > Maybe I can type, eg notice the :feature in the command > > osgi:install mvn:feature:org.apache/camel/camel-example-sql/2.11.0 > > Or some other way to install it. > > Then people just need to download Karaf, and they can install Camel > and the examples from Maven. > > Now I want them to be able to do this for their custom application as > well, so they can do > > osgi:install file:feature:/dev/myproject/target/myapp-1.0.jar > > Or something like that. > > > So how can we make it easier for people to install and try Camel > examples in vanilla Apache Karaf containers? > And how can we make it easier for people to install their own > applications in vanilla Apache Karaf containers, > which uses features.xml file to declare their dependencies. > > And NO they do NOT want to use KAR files or some Karaf specific. Their > applications should be plain JARs > that can also run outside Karaf as well. > > > > > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > FuseSource is now part of Red Hat > Email: cib...@redhat.com > Web: http://fusesource.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen > -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project Lead blog <http://notizblog.nierbeck.de/>
