[
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 this "fine print" regarding {{MessageFormat}}
somewhat hidden in the Javadoc. MessageFormat is an unfortunate choice imho.
The behavior of {{log4j-jpl}} thus has been wrong since March 2020 when the
module was first introduced?
Given its impact maybe this change should have been introduced in a Major not a
Minor release.
> log4j-jpl must handle parameters as MessageFormat args
> ------------------------------------------------------
>
> Key: LOG4J2-3345
> URL: https://issues.apache.org/jira/browse/LOG4J2-3345
> Project: Log4j 2
> Issue Type: Bug
> Components: JPL Adapter
> Affects Versions: 2.17.1
> Reporter: Carter Kozak
> Assignee: Carter Kozak
> Priority: Major
> Fix For: 2.17.2
>
>
> Currently message parameters use the configured default messagefactory, which
> provides no guarantees around the format used, however JPL API requires
> MessageFormat style formatting.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
