Re: Branding properties file not picked up by Karaf client?

For the client, you have to use branding-ssh.properties. Regards JB On Sep 21, 2016, 12:38, at 12:38, afbagwe wrote: >We are using 4.0.6. > >So I can take a pristine tar.gz of Karaf 4.0.6, drop my >branding.properties >in the etc folder and get it to show up when I run the

Re: Branding properties file not picked up by Karaf client?

We are using 4.0.6. So I can take a pristine tar.gz of Karaf 4.0.6, drop my branding.properties in the etc folder and get it to show up when I run the server in console mode. However if I do: ./start ./client (enter default Karaf password) the console comes up with the default branding instead

Re: Branding properties file not picked up by Karaf client?

Hi Allen, which Karaf version ? I fixed ssh branding recently (Karaf 4.0.6). Regards JB On 09/21/2016 07:14 PM, afbagwe wrote: We've recently switched to using the branding.properties file in the etc folder which has worked great so far. However when we start Karaf server as a background

Branding properties file not picked up by Karaf client?

We've recently switched to using the branding.properties file in the etc folder which has worked great so far. However when we start Karaf server as a background process and attempt to connect with the client is still uses the default Karaf branding page for the console interface instead of our

Re: Hot deploy priority on first start up?

JIRA ticket here. Thanks! https://issues.apache.org/jira/browse/KARAF-4723 Guillaume Nodet-2 wrote > Could you raise a JIRA for that please ? > I think I've just unwillingly reproduced the issue and I have a fix for > it. > > 2016-09-10 0:51 GMT+02:00 afbagwe > afbagwe@ > : > >> I've

RE: scr:details command

I resolved the issue that was causing the misleading display but I’ll spend a little time to see if I can recreate it. No promises but I’ll try. From: Guillaume Nodet [mailto:gno...@apache.org] Sent: Tuesday, September 20, 2016 1:43 PM To: user Subject: Re: scr:details

Re: Hot deploy priority on first start up?

Could you raise a JIRA for that please ? I think I've just unwillingly reproduced the issue and I have a fix for it. 2016-09-10 0:51 GMT+02:00 afbagwe : > I've confirmed that > > featuresBootAsynchronous=false > felix.fileinstall.active.level = 80 > > are indeed the settings

Re: Create and manager an instance using Jolokia

Hi Tom, Jolokia use the http service port. So, when you install jolokia, it installs http feature. To change the port, you have to provision org.ops4j.pax.web.cfg file containing the port property in the etc folder of the instance, or using config layer before installing the http/jolokia

Create and manager an instance using Jolokia

How do I create and then manage a new instance using jolokia? I can execute the commands on my root instance to create and start a new instance fine. On create I specify that I want "jolokia" as a feature. Fundamentally, in order to manage the second instance I have to connect directly to it

Re: Deploying an application from jenkins for test

Achim,Thanks. I'm trying to use mvn, as it does seem the best option. If I can get it to do what I want though. What I'm trying to work out is how to ensure that I get exactly the bundle that's just been published, and nothing gets cached. I'm publishing SNAPSHOT builds to our artifactory

Re: Deploying an application from jenkins for test

Hi, usually I use maven as the "transport" it's a much better integration into the CI/CD pipeline. So what I've given you as sample is optimized for exactly this. regards, Achim [1] -