I'm updating your pom.xml, I will propose a PR to you.
Regards
JB
On 14/01/2019 08:03, Jakub Herkel wrote:
> I checked org.apache.karaf.features.cfg and there was something like this
> featuresBoot = beb80995-dcae-4ab6-8c34-ba0037541e28
> and beb80995-dcae-4ab6-8c34-ba0037541e28.xml contains
I checked org.apache.karaf.features.cfg and there was something like this
featuresBoot = beb80995-dcae-4ab6-8c34-ba0037541e28
and beb80995-dcae-4ab6-8c34-ba0037541e28.xml contains features. How can I
setup two/multiple stages in this file?
I tried to reorder features manually but without success.
Hi,
I think that you need to use two stages in your boot features. As you
define activemq in boot feature, it should be in a second stage.
So, in etc/org.apache.karaf.features.cfg, I think you should have:
featuresBoot=(wrap,shell,...),activemq-broker-noweb
Regards
JB
On 13/01/2019 21:03,
Hi Matteo,
you can define a control bundle in etc/startup.properties. The bundles
define here are executed before all other steps.
Regards
JB
On 13/01/2019 22:07, Matteo Rulli wrote:
> Hello,
>
> I would like to know if there is a way in Karaf to delay the boot process
> until a specific
Hello,
I would like to know if there is a way in Karaf to delay the boot process until
a specific bundle activator has been executed. In particular, I would like to
perform some "environment validations” and checks and only if these are OK I
would like to proceed with the Karaf boot-up.
Thank
Hi,
We changed the way of loading ActiveMQ broker because:
1. we wanted to not depend on blueprint
2. blueprint container has some constraint
So, I fixed (in ActiveMQ 5.15.8) the ws connector generally speaking,
but not specifically for blueprint.
You can still use a several broker config via
Let me fix your pom.xml, but for sure, the issue is around the framework
feature.
Regards
JB
On 13/01/2019 19:48, Jakub Herkel wrote:
> I have tried to update my pom (see updated pom.xml) but I could still
> see the same exception.
>
> jakub
>
> On Sun, 2019-01-13 at 18:04 +0100, Jean-Baptiste
I have tried to update my pom (see updated pom.xml) but I could still
see the same exception.
jakub
On Sun, 2019-01-13 at 18:04 +0100, Jean-Baptiste Onofré wrote:
> Hi,
>
> Your pom.xml is not fully correct:
>
> 1. The framework features is missing:
>
>
>
Hi JB,
Ah yes, that was how we did it I believe when we were still running the 3.x
version of Karaf.
The approach I described earlier worked for Karaf 4.0.x, but no longer in
4.1.0 or newer.
It's been a while, but believe we preferred this approach for several
reasons, including that we had no
Hi,
Your pom.xml is not fully correct:
1. The framework features is missing:
org.apache.karaf.features
framework
features
xml
runtime
You have the kar, but your forgot the framework.
2. You should not use the
Hi,
I just did a quick test with Karaf 4.2.1.
Here's what I did:
1. On a fresh Karaf 4.2.1, I install the activemq-broker feature:
karaf@root()> feature:repo-add activemq 5.15.8
karaf@root()> feature:install activemq-broker
2. The activemq-broker installs etc/activemq.xml, I edited this file
I have tried to create a custom karaf distribution but I have had a
problem with an exception during startup.
org.apache.karaf.features.core[org.apache.karaf.features.internal.servi
ce.FeaturesServiceImpl] : Unknown protocol: mvn
java.net.MalformedURLException: Unknown protocol: mvn
at
12 matches
Mail list logo