I have a fork of pax-logging here: < https://github.com/jvz/org.ops4j.pax.logging> where I started working on porting some parts for log4j2.
On 21 July 2014 23:56, Jean-Baptiste Onofré <[email protected]> wrote: > Hi Matt, > > I didn't use log4j-slf4j-impl as I did a pax-logging-service native log4j > service. > However, it could be interesting as a transition to support log4jv2 > directly in Karaf without a new version of pax-logging. > Let me try it. > > Thanks for the update > > Regards > JB > > > On 07/21/2014 11:41 PM, Matt Sicker wrote: > >> Log4j2 has slf4j versions of log4j2 markers, so it would work fine to use >> the SLF4J ones. In fact, if it helps, you can use the log4j-slf4j-impl >> bundle to bridge log4j-api and log4j-core into slf4j-api. >> >> >> On 21 July 2014 14:28, Jean-Baptiste Onofré <[email protected]> wrote: >> >> Hi Gareth, >>> >>> I refactored the Markers to use slf4j marker in the case of usage of >>> slf4j >>> pax-logging-service usage, or natively log4j2 native when using log4j >>> pax-logging-service. >>> I will add a couple of unit test about that. >>> >>> Regards >>> JB >>> >>> >>> On 07/21/2014 07:36 PM, Gareth wrote: >>> >>> Hello Jean-Baptiste, >>>> >>>> I am curious - for the 1.8.0 release are you planning to do anything >>>> different with Markers? I understand that Pax Logging currently converts >>>> any >>>> Markers into an MDC parameter (slf4j.marker) because log4j doesn't >>>> support >>>> them. However both log4j2 and logback do support Markers natively. Just >>>> curious. >>>> >>>> thanks in advance, >>>> Gareth >>>> >>>> >>>> >>>> -- >>>> View this message in context: http://karaf.922171.n3.nabble. >>>> com/Any-news-on-the-Log4j-2-upgrade-tp4034325p4034344.html >>>> Sent from the Karaf - Dev mailing list archive at Nabble.com. >>>> >>>> >>>> -- >>> Jean-Baptiste Onofré >>> [email protected] >>> http://blog.nanthrax.net >>> Talend - http://www.talend.com >>> >>> >> >> >> > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com > -- Matt Sicker <[email protected]>
