Hi, Just to be clear: org.osgi.service.log is provided by Pax Logging (not Karaf directly). The version is set by Pax Logging.
org.osgi.service.log 1.4 is part of R7, so it requires Pax Logging 2.0.0. Karaf 4.2.x is R6, so it needs some changes to support pax-logging 2.0.0 but do-able (not a big effort, pretty easy). So, my proposal is: 1. I do Pax Logging 2.0.0 release 2. I upgrade Pax Logging on karaf master to cut 4.3.0.RC1 (R7 compliant) 3. Once Karaf 4.2.8 is released (it will happen this week), I will update on 4.2.9-SNAPSHOT to evaluate support of Pax Logging 2.0.0 (and update command and so). If good, I will prepare 4.2.9 with that. Does it sound good to you ? Regards JB On 08/01/2020 14:06, Markus Rathgeb wrote: > Hi, > > it's more Pax Logging related. > > > hm, I updated (on december) a Karaf instance to use the most recent > (that time) 2.0.0 SNAPSHOT and the only breakage I identified at that > time is the Karaf integration itself (org.apache.karaf.log.core) -- > missing commands etc. > So for me Pax Logging has been already ready (more or less) but the > Karaf side cannot use it. > But I did not do excessive testing. > > In the long run I will definitely move to 4.3.0 but this is a bigger > change that cannot be done such easily (testing etc) than moving from > 4.2.7 to 4.2.8. > > Best regards, > Markus -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
