Hi Brad Unfortunately I don't have access to my development computer so can't send you the example today. But let me explain a bit more what I meant.
What I do is I basically create a complete custom distribution of Karaf together with all necessary bundles (Camel and all the rest) and include them as boot level features. This means that when Karaf is started, the bundles are already active. You don't need to add anything to the deploy folder or do any maven stuff. All you do is unzip and run karaf and the camel bundles and everything else is started. It is one way of creating a custom distribution of Karaf for your Camel routes and isolate them. The way I do it is simply to create a pom file and add a few maven plugins and state certain Karaf features. Then I just run clean install either on my machine or via jenkins and the custom distribution is built. Then you just deliver it to your server and unzip it..or in our case we put it inside docker and run it there. We don't do anything else afterwards. No deploys to deploy folder or run maven commands. You can customise the logging config and other stuff as well. If this still sounds interesting let me know and I can e-mail you an example. For more info see here: http://karaf.apache.org/manual/latest/#_custom_distributions On Wed, Nov 2, 2016 at 7:20 PM, Souciance Eqdam Rashti < souciance.eqdam.ras...@gmail.com> wrote: > Hi Brad, that's not what I meant, will send you an example later to see. > > Den 2 nov. 2016 6:10 em skrev "Brad Johnson [via Camel]" < > ml-node+s465427n5789661...@n5.nabble.com>: > >> Most of what I need is already in the features installed in the AMQ. This >> is more a matter of pulling my items together and installing them as a >> feature. Obviously I could do that locally where I can install it in MVN >> and then put the url in on the karaf command line and run the install. I >> could drop bundles in the deploy directory as well. Not crazy about that >> though. I just need a way to list the camel features to install, the >> libraries I need, and all that in a standard features file but then make >> it >> available in karaf without using the mvn:addurl >> >> On Wed, Nov 2, 2016 at 10:13 AM, souciance <[hidden email] >> <http:///user/SendEmail.jtp?type=node&node=5789661&i=0> >> > wrote: >> >> > I am not sure this is what you want but I have created a custom >> > distribution for Karaf that includes all my bundles for Camel and >> > everything else and you can then specify your config files. It is a pom >> > based config and after doing a clean install you get a zip and tar.gz >> file. >> > You can then upload that to your server, unzip and run karaf. >> > >> > On Wed, Nov 2, 2016 at 4:09 PM, Brad Johnson [via Camel] < >> > [hidden email] <http:///user/SendEmail.jtp?type=node&node=5789661&i=1>> >> wrote: >> > >> > > Are there any good examples of creating an assembly to install my >> bundles >> > > into a standalone karaf/AMQ instance. I'm used to working with the >> Fuse >> > > stack where creating a features file, adding the url via mvn:install, >> > and >> > > then doing the mvn:install installs all my requirements and cfg >> files. >> > So >> > > the features file and listing the required bundles for installation >> is a >> > > well known task. >> > > >> > > I'm in a situation where there isn't a Maven repo available so all >> the >> > > dependencies need to be included in the assembly. >> > > >> > > I've found some examples that show the use of the assembly for >> pulling >> > > together the entire stack but that's obviously much larger than I'm >> > > looking >> > > for. Just want to create the assembly, put it in the right location >> in >> > > the >> > > karaf/AMQ standalone instance, and then probably run the features >> file to >> > > install the required bundles. >> > > >> > > >> > > ------------------------------ >> > > If you reply to this email, your message will be added to the >> discussion >> > > below: >> > > http://camel.465427.n5.nabble.com/AMQ-Camel-assembly-tp5789652.html >> > > To start a new topic under Camel - Users, email >> > > [hidden email] >> <http:///user/SendEmail.jtp?type=node&node=5789661&i=2> >> > > To unsubscribe from Camel - Users, click here >> > > <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro= >> > unsubscribe_by_code&node=465428&code=c291Y2lhbmNlLmVxZGFtLnJhc2h0aU >> > BnbWFpbC5jb218NDY1NDI4fDE1MzI5MTE2NTY=> >> > > . >> > > NAML >> > > <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp? >> macro=macro_ >> > viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces. >> >> > BasicNamespace-nabble.view.web.template.NabbleNamespace- >> > nabble.view.web.template.NodeNamespace&breadcrumbs= >> > notify_subscribers%21nabble%3Aemail.naml-instant_emails% >> > 21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> >> > > >> > >> > >> > >> > >> > -- >> > View this message in context: http://camel.465427.n5.nabble. >> > com/AMQ-Camel-assembly-tp5789652p5789653.html >> > Sent from the Camel - Users mailing list archive at Nabble.com. >> >> >> ------------------------------ >> If you reply to this email, your message will be added to the discussion >> below: >> http://camel.465427.n5.nabble.com/AMQ-Camel-assembly-tp57896 >> 52p5789661.html >> To start a new topic under Camel - Users, email >> ml-node+s465427n465428...@n5.nabble.com >> To unsubscribe from Camel - Users, click here >> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=465428&code=c291Y2lhbmNlLmVxZGFtLnJhc2h0aUBnbWFpbC5jb218NDY1NDI4fDE1MzI5MTE2NTY=> >> . >> NAML >> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> >> > -- View this message in context: http://camel.465427.n5.nabble.com/AMQ-Camel-assembly-tp5789652p5789673.html Sent from the Camel - Users mailing list archive at Nabble.com.
