[ https://issues.apache.org/jira/browse/LOG4J2-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14095818#comment-14095818 ]
Gary Gregory commented on LOG4J2-774: ------------------------------------- I think we should leave the default as it is or improve it such that it becomes machine parsable more easily. A blank separated list of values does not account for embedded blanks and current format has it machine parsable issues as well I am sure. I have not looked in detail in a while. I would support and document some configuration option that is 1.2 compatible since we have a request for it. I would not hold up 2.0.2 for this though, it can go in 2.0.2, or 2.1 IMO. > NdcPatternConverter breaks Log4j 1.2.x layout > --------------------------------------------- > > Key: LOG4J2-774 > URL: https://issues.apache.org/jira/browse/LOG4J2-774 > Project: Log4j 2 > Issue Type: Bug > Components: Layouts > Affects Versions: 2.0.1 > Reporter: Frank Wißmann > Assignee: Remko Popma > Priority: Minor > Labels: patch > Fix For: 2.0.2 > > Attachments: NdcPatternConverter.java.patch > > > In Log4j 1.2.17 NdcPatternConverter.format() returns an empty string "" or > the stack messages separated by space "a b c" > (NDC.DiagnosticContext.fullMessage). > The PatternLayout \[%20.20x\] results in > {code}[ ]{code} or {code}[ a b c]{code}. > In Log4j 2.0.1 NdcPatternConverter.format() returns an unmodified > Collection.toString() representation: "\[\]" for an empty collection or the > collection separated by comma "\[a, b, c\]" > (DefaultThreadContextStack.toString() and > MutableThreadContextStack.toString()). > The PatternLayout \[%20.20x\] results in {code}[ []]{code} > or {code}[ [a, b, c]]{code}. -- This message was sent by Atlassian JIRA (v6.2#6252) --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org