Re: 4.1.5 and Karaf Maven Plugin

François is right: you repo requires an authentication. So, check your settings in term of user/password. Regards JB On 02/26/2018 03:06 AM, François Papon wrote: > Hi, > > Your repository mvnrepo:8080 required an authentication (401). Are you using > the > same repository when you build on

Re: 4.1.5 and Karaf Maven Plugin

Hi, Your repository mvnrepo:8080 required an authentication (401). Are you using the same repository when you build on local ? May be your old job is ok because the artefacts already are in the workspace of Jenkins. Francois Le 25 févr. 2018 23:50, Ryan Moquin a écrit

Re: Using jasypt in Karaf 4.1.4 without Blueprint?

One way I handled this in the past (though I'm not overly fond of the solution since it relied on AWS, but it would be interesting if there was a generic way to achieve it), was to use AWS KMS and role based authentication. This way the instance could decrypt it's password from the ec2 instance

Re: Regarding Configuration Types

If trimming was performed by default on tproperties, wouldn't that place a little extra performance overhead into OSGi vs developers just making sure there isn't trailing whitespace if they don't want it? It wouldn't be much, but it adds up... Ryan On Thu, Feb 22, 2018 at 12:52 PM Leschke,

Karaf distributions and system repository

When building a karaf distribution, I have my main features xml defined in runtime scope but non of the features as installed or boot features. This results in the features xml file being copied to the system repository of the distribution. This is handy since I can skip the feature:repo-add

4.1.5 and Karaf Maven Plugin

Has anyone had any weird issues with the karaf-maven-plugin having issues pulling the framework features xml when building a distribution? After switching to 4.1.5, our jenkins build fails due to a 401 trying to retrieve the 4.1.5 features xml when building a distribution. If I change the

Re: Karaf 4.1.0.M2 Feature Verification

O, duh. I knew I had saw a Karaf feature that had the other spring versions in it. That explains a lot. I remember seeing that legacy one in the past, my bad. Thanks for clarifying! Ryan On Sat, Feb 24, 2018 at 10:12 PM Jean-Baptiste Onofré wrote: > Yes, that's