You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/01/18 01:40:00 UTC

[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:
---------------------------------------------------------

Commit 36585cf45e0925fb50f6cb469f9bf49cad793369 in logging-log4j2's branch refs/heads/release-2.x from Carter Kozak
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=36585cf ]

LOG4J2-3345: log4j-jpl formats messages correctly using MessageFormat (#713)



> 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
>
> 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)