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 <christianl...@kreeloo.de> a écrit : > > 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 <j...@nanthrax.net>: >> >> 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 <slesc...@medline.com >>> <mailto:slesc...@medline.com>> a écrit : >>> >>> 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 >>> installed I’m wondering what might could cause this to occur now. The log >>> doesn’t show anything out of the ordinary. >>> >>> As a sanity check, I tried dropping back to v4.2.7 and get the same >>> behavior. I’m thinking that some Karaf dependencies have been updated that >>> could be causing this even though the version hasn’t changed but I’m also >>> wondering if something in my environment could cause it. >>> >>> Thoughts? >>> >>> Scott >>
