Karaf Decanter 2.3.0 has been released! April 6, 2020
This is a first minor release for Apache Decanter 2.3.x, containing bug fixes,
improvements and dependency upgrades.
Among this new features, we have:
Add prometheus appender
Improve Decanter alerting by supporting time series and
It’s more or less what docker:provision is doing ;)
Regards
JB
> Le 7 avr. 2020 à 17:52, Gerald Kallas a écrit :
>
> Hi, that's the way I did w/ Camel on Karaf
>
> 1. Start karaf
>
> cd /opt
> unzip /home/karaf/apache-karaf-4.2.7.zip
> ln -s /opt/apache-karaf* /opt/apache-karaf
> cd
Hi Team
Using Karaf 4.2.6
Want to understand why karaf listens to HUP signal? and why is it handled to
generate dump-.zip
files?
One more observation in karaf 4.2.6
1. the time when the dump-.zip is generated in KARAF_HOME folder,
there is also a file in KARAF_TMP folder with name
There is a new version of the Jersey Distribution Provider [1] for ECF's
impl of OSGi R7 Remote Services. The new version uses Jersey 2.30.1 and
depends upon an updated version of ECF (3.14.6)
ECF's impl of the OSGI R7 Remote Services Specification [2] allows for
pluggable transports known
Hello,
I just wanted to ask if someone has a running karaf 4.2.8 instance with REST
services protected by keycloak.
Based on this
https://github.com/jboss-fuse/karaf-quickstarts/tree/7.x.redhat-7-x/security/keycloak/keycloak-cxf#testing-embedded-undertow-servlet-engine
Hi, that's the way I did w/ Camel on Karaf
1. Start karaf
cd /opt
unzip /home/karaf/apache-karaf-4.2.7.zip
ln -s /opt/apache-karaf* /opt/apache-karaf
cd apache-karaf/bin
./karaf
2. Install the needed features (in a 2nd SSH session)
cd /opt/apache-karaf/bin
./client < karaf.sh
karaf.sh looks
Hi JB,
that's true and sorry, we did not want to deny the dynamic flexibility at
all ...
as we use it also in our projects but need urgent a static alternative to
get more robust on special use cases.
Regards
Stefan
jbonofre wrote
> Hi,
>
> I think it depends of the use case. I fully
Hi JB,
we are very interested on that material because we think a static
distribution is the only way (after many years of Experience with Karaf) to
get a robust and well defined Platform for the Enterprise
Regards
Stefan
jbonofre wrote
> That’s actually a great news ! It’s great to
Hi,
I think it depends of the use case. I fully understand people like you using
static distribution, but I also understand people using dynamic distribution.
So, I got your point and I agree. The huge advantage of Karaf is the
flexibility: it can address very different use cases and
That’s actually a great news ! It’s great to see people using static
distribution !
By the way, we are working on new tooling to even easily create distribution
(static or dynamic) !
The purpose is to provide a much better dev experience.
I will prepare some materials to discuss on the mailing
> Steinar Bang :
> Is there a way to flush what docker:provision has made?
Yes. Use the "docker" command on the host (docker installed with
"apt install docker.io" on a debian stable system):
docker rm -vf $(docker ps -a -q)
docker rmi -f $(docker images -a -q)
Source:
Hi JB,
thanks a lot for explaining this.
So we stay on 4.2.6 and waiting for 4.2.9 because static distribution is
urgent to us as you know.
Regards
Stefan
jbonofre wrote
> Hi Stefan,
>
> If the problem is related to PAX JDBC in static distribution, it’s not yet
> fully fixed.
>
> All the
Hi Erwin,
we tried it with static distribution based on 4.2.8 Release without any luck
(4.2.6 without problems)
Anything we missed?
Regards
Stefan
Erwin Hogeweg wrote
> Hi Lukas,
>
> Glad I could help.
>
> Happy coding.
>
> Erwin
>
>
>> On Mar 18, 2020, at 12:13, Roedl Lukas
>
Hi Stefan,
If the problem is related to PAX JDBC in static distribution, it’s not yet
fully fixed.
All the details is in the Jira: the problem is about the resolver order. When
using static distribution, all features are startup features, meaning that all
is evaluated at same stage. As PAX
> Jean-Baptiste Onofre :
> You just need the docker daemon running on the same machine where Karaf is
> running: docker feature interacts with the docker daemon (it could be remote
> also).
> You can pass the URL as argument, for instance docker:provision —url
> http://localhost:2375
Probably we will use custom distribution. What we need is packaging karaf
with our application and also to add some additional customizations
(additional JVM options, environment variables).
But for development we will use "pure" karaf because this custom
distribution we need only for deployment
16 matches
Mail list logo