[jira] [Commented] (LOG4J2-3345) log4j-jpl must handle parameters as MessageFormat args

[ https://issues.apache.org/jira/browse/LOG4J2-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504312#comment-17504312 ] Markus Spann commented on LOG4J2-3345: -- [~ckozak] I must admit I was not aware of

[jira] [Commented] (LOG4J2-3345) log4j-jpl must handle parameters as MessageFormat args

[ https://issues.apache.org/jira/browse/LOG4J2-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503605#comment-17503605 ] Carter Kozak commented on LOG4J2-3345: -- The System.Logger API that this implements

[jira] [Commented] (LOG4J2-3345) log4j-jpl must handle parameters as MessageFormat args

[ https://issues.apache.org/jira/browse/LOG4J2-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503589#comment-17503589 ] Markus Spann commented on LOG4J2-3345: -- [~ckozak], this is a breaking change for ap

[jira] [Commented] (LOG4J2-3345) log4j-jpl must handle parameters as MessageFormat args

[ https://issues.apache.org/jira/browse/LOG4J2-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477512#comment-17477512 ] ASF subversion and git services commented on LOG4J2-3345: - Commi

[jira] [Commented] (LOG4J2-3345) log4j-jpl must handle parameters as MessageFormat args

[ https://issues.apache.org/jira/browse/LOG4J2-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477510#comment-17477510 ] ASF subversion and git services commented on LOG4J2-3345: - Commi