As we switched to log4j2 configuration style, we now use pax-logging-log4j2.

pax-logging-log4j2 replaces the pax-logging-service (log4j1 style)
implementation of pax-logging-api.

I guess you use a fragment to use a log4j appender ?

If so, you should update your appender to log4j2 style and attach to
Even better is to implement your PaxAppender (based on the pax-logging-api).


On 03/02/2018 09:58 AM, munishgupta.asr wrote:
> Hi All,
> for our project, we are using KARAF 4.0.9 for now and decided to upgrade it
> to 4.1.5.
> we have a customer appender which is used as a fragment with
> pax-logging-service bundle. 
> After upgrading to KARAF 4.1.5, it is failing to find pax-logging-service
> and service is not getting downloaded in system folder using maven.  rather
> I could see 2 different folders in system path.
> Pax-logging-logback
> pax-logging-log4j2
> have we removed support of pax-logging-service with KARAF 4.1.x onwards.
> What shall i use now as fragment-host bundle to get the build generated?
> Regards
> Munish 
> --
> Sent from: http://karaf.922171.n3.nabble.com/Karaf-Dev-f930721.html

Jean-Baptiste Onofré
Talend - http://www.talend.com

Reply via email to