On Fri, Jan 18, 2013 at 3:17 PM, Guillaume Nodet <[email protected]> wrote: > Fwiw, when you use the url handler or drop the file in the deploy folder, > both methods just generate a bundle which has the feature file inside > META-INF/org.apache.karaf.shell.features >
I cannot find any details about this in the docs. So maybe its an "hidden" feature. Though as I could not get it working. I would be good if a Karaf committer could take a look in the source code. As an end user I would love this to work. Its then much easier to deploy your applications to Karaf, as you can include the features.xml file that refers to the dependencies. Then the deploy is very easy as its either - drop file to deploy dir - use one line command from shell - possible deploy from web console, if it has such functionality to upload a file. Any thoughts? > > On Fri, Jan 18, 2013 at 2:53 PM, Achim Nierbeck > <[email protected]>wrote: > >> Oh well, >> >> didn't remember the last possibility of the features-deployer :) >> >> thanks, Achim >> >> >> 2013/1/18 Guillaume Nodet <[email protected]> >> >> > Are you talking about the features deployer ? >> > Karaf has it already. You can use osgi:install feature:mvn:xxx or drop >> the >> > features file in the deploy directory, or deploy any bundle which has a >> > META-INF/org.apache.karaf.shell.features/*.xml file inside. >> > >> > >> > On Fri, Jan 18, 2013 at 12:46 PM, Achim Nierbeck < >> [email protected] >> > >wrote: >> > >> > > 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 <[email protected]> >> > > >> > > > 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: [email protected] >> > > > 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/> >> > > >> > >> > >> > >> > -- >> > ------------------------ >> > Guillaume Nodet >> > ------------------------ >> > Blog: http://gnodet.blogspot.com/ >> > ------------------------ >> > FuseSource, Integration everywhere >> > http://fusesource.com >> > >> >> >> >> -- >> >> 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/> >> > > > > -- > ------------------------ > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > FuseSource, Integration everywhere > http://fusesource.com -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
