You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Markus Spann (Jira)" <ji...@apache.org> on 2022/03/09 13:25: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=17503589#comment-17503589 ] 

Markus Spann commented on LOG4J2-3345:
--------------------------------------

[~ckozak], this is a breaking change for applications developed against System Logger and expecting the curly braces pattern without indices.

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