Karaf 4.2.8 already includes use of https in etc/org.ops4j.pax.url.mvn.cfg so I
don’t think it’s the problem.
Regards
JB
> Le 19 mai 2020 à 07:12, Christian Lutz a écrit :
>
> Good morning,
>
> one problem we had was that maven requires https now. Look into ...mvn.cfg
> repositories. If the
Good morning,
one problem we had was that maven requires https now. Look into ...mvn.cfg
repositories. If the s is missing add it and your fine.
kind regards.
Christian
> Am 19.05.2020 um 06:55 schrieb Jean-Baptiste Onofre :
>
> Hi Scott,
>
> All "core" dependencies are in system folder,
Hi Scott,
All "core" dependencies are in system folder, so I don’t think it’s related.
I’m more suspecting some environment changes (JDK, env variables), like shell,
locale, ...
Still the same if you purge the data folder ?
Regards
JB
> Le 19 mai 2020 à 04:38, Leschke, Scott a écrit :
>
> I
I've been running 4.2.8 for months (on Win64) without any issues but after I
did a reinstall on my test system last week, Karaf comes up with many of the
commands not being recognized, like the "bundle" commands, "source" and
"logout" for example. Since this issue didn't exist when I originally
Thank you Łukasz, JB and Erwin. I’ll deep dive on it.
> On 17 May 2020, at 22:16, Erwin Hogeweg wrote:
>
> Hi Davi,
>
> You can absolutely use the EventAdmin for your ‘own’ events. There are many
> ways to accomplish this. My preference is to use the component annotations.
>
> The class that
Hi,
store your secrets as bash script with
key=value
and include the secret in your start script
. /run/secrets/credentials.sh
Now the secrets are available as shell environment.
Regards,
Mike
> On 5. May 2020, at 22:16, Alex Soto wrote:
>
> I found using Docker Secrets a convenient a wa
Good Morning.
Please correct me if I'm wrong. I have seen that datasources are shared
between instances. This means that if an org.ops4j.datasource-.cfg file is
created in one instance, the Datasource is available in all the others.
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930
I don't think it is mainly for internal stuff. For example openHAB
project makes rather intense use of event admin masked under
org.openhab.core.events.EventPublisher and
org.openhab.core.events.EventSubscriber interfaces.
Main point for above abstraction is separation of application specific
logic