usually I use maven as the "transport" it's a much better integration into
the CI/CD pipeline.
So what I've given you as sample is optimized for exactly this.
2016-09-20 9:22 GMT+02:00 <t...@quarendon.net>:
> > you can use Pax Exam for that and start Karaf embedded, this will give
> > you a clean state for every run.
> Initially I want to do it for testing, but I then want to deploy a
> and "release" version of the actual application for general internal demo
> use. I
> currently already have an integration test suite, but what it doesn't test
> the deployment into karaf, so I want to deploy it for testing in a way
> that is
> as close to the real thing as possible.
> > The other way would be to have a Karaf with Jolokia running and deploy
> > JMX, I once created a sample for that .
> As I say, my question was really one of what the transport is for the
> One way of the other I invoke the equivalent of "feature:add-repo", then
> "feature:install", my question is what are the URLs, where does karaf
> pull stuff from. To use mvn repositories I need to find a way of turning
> off the
> caching, which so far I've failed to do. Pushing the files on to the remote
> machine using SCP and then addressing them with "file:///" URLs seems
> way, but it seems over complicated to push them. Addressing the artifacts
> jenkins directly is another way, but it seems like I'm going to have to
> something bespoke to create a feature repository with the correct URLs in
> some kind of template (substituting the correct build number in all of the
> Just hoping there might be a known best way to do this kind of thing, save
> figuring it out!
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master