Hi Alex,
4.2.2 is not yet released. The vote is scheduled for next week, so
hopefully, it could be available on Central in 2 weeks.
Regards
JB
On 21/11/2018 21:41, Alex Soto wrote:
> I am starting to upgrade Karaf to version 4.2.2, plugin
> /karaf-maven-plugin /is missing:
> I get error:
>
>
Hi Alex,
FYI, Karaf 4.2.2 isn't released yet, should be available in coming weeks.
Cheers
Freeman
－
Freeman(Yue) Fang
Red Hat, Inc.
> On Nov 22, 2018, at 4:41 AM, Alex Soto wrote:
>
> I am starting to upgrade Karaf to version 4.2.2, plugin karaf-maven-plugin
> is missing:
I am starting to upgrade Karaf to version 4.2.2, plugin karaf-maven-plugin is
missing:
I get error:
Could not find artifact
org.apache.karaf.tooling:karaf-maven-plugin:jar:4.2.2 in central
(https://repo.maven.apache.org/maven2) @
Was this renamed or moved somewhere else?
Best
On Wed, Nov 21, 2018 at 11:23 AM Ranx wrote:
> Raymond,
>
> Thanks for the information. I was probably unaware of the RI because it
> isn't listed on the Aries website
Good point! So I did some updates to the main page [1]. I will try to make
further updates to other pages as time permits.
A possible reason could be lots of DS services with greedy optional static
dependencies started in different orders on the two OSs. If a service with such
a reference is started first, it will get restarted every time a target service
for the reference is started.
David Jencks
Sent from my
Raymond,
Thanks for the information. I was probably unaware of the RI because it
isn't listed on the Aries website and the only annotations I was aware of
from there were the Blueprint annotations. Also, PAX CDI has been installed
in Fuse for some time now although in the 6.x version (Karaf 2.x)
Thanks. I'll give it a look.
Unfortunately, as a consultant I'm not at liberty to choose the
implementation I use. My clients are, by and large, using Red Hat Fuse.
Currently Fuse 7 is preloaded with PAX CDI but it sounds as if that may not
remain the same. There have been a number to technology
There is a whole lot of assumptions going on here and before conjecture
wins the day I want to make some corrections:
- OSGi CDI Integration is *completely reactive to both Services and
Configuration*. See the spec [1]
- *Aries CDI is the RI and is very active*. See the commit history [2]
-
The hot deploy folder hierarchy being scanned is CIFS but it is not under /etc.
My hot deploy is a folder directly under C:/. It's been this way for a long
time.
Scott
-Original Message-
From: Jean-Baptiste Onofré
Sent: Wednesday, November 21, 2018 9:25 AM
To: user@karaf.apache.org
Let me start a Windows VM to try to reproduce.
According to the trace, it's certainly related to environment (Windows,
...).
By the way, is etc folder on CIFS or a shared volume ?
Regards
JB
On 21/11/2018 16:17, Leschke, Scott wrote:
> I’ve retested this a couple of times in the last hour.
I've retested this a couple of times in the last hour. It's reasonably
repeatable but is relatively new behavior in 4.2.1 as far as I can tell. It
looks like the following is the cause of the behavior. It appears repeatedly
in the log file.
2018-11-21T09:05:29,272 | ERROR |
It still begs the question as to why you saw such a difference in times between
Windows and Mac.
From: Oleg Cohen
Sent: Tuesday, November 20, 2018 11:34 PM
To: user@karaf.apache.org
Subject: Re: Startup timing Windows vs. Mac
Hi JB,
Thank you for the clarification. I think the bundle load
If you really want to pick a CDI implementation to use in Karaf, I would
advise to look at the CDI RI from Aries.
It appears that the spec has evolved in the right direction, also it's
still very limited in terms of beans lifecycle.
The main problem imho is that the spec does not allow tying the
13 matches
Mail list logo
