Hi

What do you want to achieve exactly ?
Creating a custom distro on Jenkins ? Updating a remote running instance of 
karaf ?

Regards
JB

On Nov 21, 2017, 15:27, at 15:27, smunro <stephen.ross.mu...@gmail.com> wrote:
>I'm still trying to get an offline installation of karaf working, which
>is
>providing to be the stuff of nightmares. To get around this problem, I
>have
>attempted download karaf on the CI server and execute a series of
>feature:install commands.
>
>The problem is that when karaf is installed on the target machine, I
>get a
>series of errors such as the following:
>
>org.osgi.service.cm.ConfigurationException: null : Cannot start the
>broker
>       at
>org.apache.activemq.osgi.ActiveMQServiceFactory.updated(ActiveMQServiceFactory.java:144)
>[101:org.apache.activemq.activemq-osgi:5.14.5]
>       at
>org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.updated(ManagedServiceFactoryTracker.java:159)
>[7:org.apache.felix.configadmin:1.8.16]
>       at
>org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.provideConfiguration(ManagedServiceFactoryTracker.java:93)
>[7:org.apache.felix.configadmin:1.8.16]
>       at
>org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUpdate.provide(ConfigurationManager.java:1640)
>[7:org.apache.felix.configadmin:1.8.16]
>       at
>org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUpdate.run(ConfigurationManager.java:1582)
>[7:org.apache.felix.configadmin:1.8.16]
>       at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:141)
>[7:org.apache.felix.configadmin:1.8.16]
>       at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:109)
>[7:org.apache.felix.configadmin:1.8.16]
>       at java.lang.Thread.run(Thread.java:748) [?:?]
>Caused by: java.io.FileNotFoundException: class path resource
>[home/bamboo-agent/bamboo-agent-home/xml-data/build-dir/bamboo_job/apache-karaf-4.1.3/etc/activemq.xml]
>cannot be resolved to URL because it does not exist
>
>So after performing the feature:install, it has preserved the path that
>the
>feature was installed on. Is there a way to get around this? I've tried
>the
>karaf-assembly plugin, but the problem is that I need to use an
>external
>feature file as the inline pom does not support <wrap> or <configfile>
>only
><feature>
>
>
>
>--
>Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html

Reply via email to