Yes. I just tried on Centos 7.7 the result was the same.
- Bob
On 2020/01/31 15:09:55, Jean-Baptiste Onofré wrote:
> Any chance to test on Unix ?
>
> Regards
> JB
>
> On 31/01/2020 15:55, Bob Paulin wrote:
> > Hi JB,
> > Thanks for taking a look. I used windows for my test. Also the referen
Any chance to test on Unix ?
Regards
JB
On 31/01/2020 15:55, Bob Paulin wrote:
> Hi JB,
> Thanks for taking a look. I used windows for my test. Also the reference
> urls was a layover from playing around with static distributions so that can
> be removed. For my particular usecase static was
Hi JB,
Thanks for taking a look. I used windows for my test. Also the reference urls
was a layover from playing around with static distributions so that can be
removed. For my particular usecase static was too static (needed to support
config changes). I've put all this into a JIRA
https://
Hi Bob,
Thanks for sharing, I will try to reproduce and fix.
By the way, are you on Windows or Unix ?
I already have a question: why do you use reference URLs without static
distribution ?
Regards
JB
On 31/01/2020 04:45, Bob Paulin wrote:
> Hi,
>
> I'm getting a similar error trying to run th
Hi,
I'm getting a similar error trying to run the standard feature as a
startup feature. Everything seems to still startup fine but the logs
are noisy at the beginning. Am I doing something wrong or unsupported:
My pom.xml
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/200
> -Original Message-
> From: Jean-Baptiste Onofré
> Sent: Tuesday, May 21, 2019 9:33 PM
> To: user@karaf.apache.org
> Subject: Re: Get NPE in FeatureDeploymentListener.bundleChanged()
>
> Hi,
>
> It seems that your feature is changing the OSGi framework state
Hi,
It seems that your feature is changing the OSGi framework state and ROOT
REGION.
Can you please share your features XML ?
That's probably a mistake in the req/cap of your features.
Regards
JB
On 21/05/2019 22:30, KARR, DAVID wrote:
> I'm working with a team that is trying to upgrade a lega
I'm working with a team that is trying to upgrade a legacy service from Karaf
3.0.1 to 4.2.5. When they try to deploy it, they're seeing the following:
---
2019-05-15T21:45:36,871 | INFO | activator-1-thread-2 | Activator
| 12 - org.apache.karaf.d
