Build failed in Jenkins: Log4j 2.x #1930

See Changes: [rpopma] LOG4J2-1179 added section on parameterized message logging [rpopma] LOG4J2-1179 highlight the conclusion of the parameterized message [rpopma] LOG4J2-1179 small fixes in section on parameterized message logging [rpo

Re: Interesting little read

>For what it is worth, my own advice is that libraries and framework developers should always include the slf4j-nop if they use slf4j-api. If their end-users want logging, they can always use dependency exclusions to enable it. That sounds like it'd make it harder for the users than necessary. Plu

Re: Interesting little read

Maybe, but I can’t really agree with his conclusion. Ralph > On May 5, 2016, at 12:40 PM, Gary Gregory wrote: > > http://www.russet.org.uk/blog/3112 > > G > > -- > E-Mail: garydgreg...@gmail.com | > ggreg...@apache.org

Interesting little read

http://www.russet.org.uk/blog/3112 G -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition JUnit in Action, Second Edition Spring Batch in Action

[jira] [Updated] (LOG4J2-1179) Log4j performance documentation

[ https://issues.apache.org/jira/browse/LOG4J2-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1179: Attachment: ParamMsgThrpt4T.png ParamMsgThrpt2T.png ParamMsgThrpt1T.