karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arunan Balasubramaniam <arunan.balasubraman...@interlinksoftware.com>
Subject RE: Half patch for logging documentation
Date Tue, 23 May 2017 08:05:17 GMT

Hi Matt,

You don’t always need to specify a context prefix - https://logging.apache.org/log4j/2.x/manual/configuration.html#PropertySubstitution
hence all the ${karaf.foo} ones etc are fine as are the locally defined properties like ${log4j2.pattern}.
It would be good to document what properties are in the default context but I don't actually
know what the answer to that one is!


-----Original Message-----
From: Matt Sicker [mailto:boards@gmail.com] 
Sent: 22 May 2017 17:05
To: Karaf Developers List <dev@karaf.apache.org>
Subject: Re: Half patch for logging documentation

I think you need to specify which lookup to use in ${placeholder} things in the log4j2 properties
file example. For example: ${sys:foo.bar} for the foo.bar system property. < https://logging.apache.org/log4j/2.x/manual/lookups.html>

I'm not sure what happens when you don't use a prefix as it's not clearly documented.

On 22 May 2017 at 08:32, Arunan Balasubramaniam < arunan.balasubramaniam@interlinksoftware.com>

> Hi,
> the user documentation still refers to configuring logging using 
> log4j(1) while Karaf has moved on to log4j2. I started updating the 
> documentation but did not feel confident changing anything from the 
> "Advanced configuration" stage towards the bottom of the 
> documentation. The changes I made up to that point are available at 
> https://github.com/NetNow/
> karaf/commit/e0a592117bb259833f8500c6c534c2f1deb13d22 in case they are 
> of use; but if that commit were applied as-is, the manual would have 
> instructions for both log4j and log4j2 configuration in it which is 
> possibly worse than now.
> By the way, the file etc/org.ops4j.pax.logging.cfg has a few log4j(1) 
> properties left in but commented out at the bottom.
> Regards,
> Arunan

Matt Sicker <boards@gmail.com>
View raw message