Hi JB,
For our application we deploy it through a feature file. But we can
recreate the issue by getting a fresh karaf 4.1.1 and directly coping the
bundle jna 4.3.0 to deploy folder there. The log I had attached was from
this scenario. Note the karaf startup logs at the end, it kind of
Hi,
do you directly deploy the JNA bundle ?
Can you describe a bit the steps you do ?
Thanks !
Regards
JB
On 06/02/2017 07:10 AM, Shyalika Benthotage wrote:
Hi,
We have been using 3.0.3 for some time now and trying to migrate to karaf 4.x.
As a part of our application, when I try to deploy
The difference between 4.1 and 4.2 is that with 4.2, both cfg and config
files can hold typed or untyped configurations and karaf will switch to a
typed configuration automatically if needed. The syntax will be the same
however. And there's currently no ETA defined.
2017-06-01 23:21 GMT+02:00
From your answer I gather this will be fully sussed out in 4.2, i.e. .cfg will
be supported and the syntax may change somewhat. Is there an ETA on that
release?
From: Guillaume Nodet [mailto:gno...@apache.org]
Sent: Thursday, June 01, 2017 4:11 PM
To: user
Subject: Re:
First, it has to be xx.config not xx.cfg. Before 4.2, both are handled
differently.
So in 4.1, you need to use the config syntax:
myInts = i[ "10", "5", "4" ]
See the syntax description:
The status of this is listed as fixed as of 4.1 but I can't seem to get it to
work. I'm trying to set an int[] neither of the following worked. I get a
NumberFormatException complaining about input string "{15,10,5}" or
alternatively "[15,10,5]";
myInts = {10,5,0};
myInts = [10,5,0];
There's
> Steinar Bang :
> Steinar Bang :
> Castor :
>>> That's weird, i'm using the liquibase-slf4j as a fragment for quite
>>> sometime and i don't have this problem. but i'm using Karaf 4.0.8, and
>>> if i'm correct karaf 4.1.x changed some
> Steinar Bang :
> Castor :
>> That's weird, i'm using the liquibase-slf4j as a fragment for quite
>> sometime and i don't have this problem. but i'm using Karaf 4.0.8, and
>> if i'm correct karaf 4.1.x changed some stuff related to logging,
>> could be