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/08/22 21:07:00 UTC
[jira] [Commented] (LOG4J2-2557) Improved printf() support.
[ https://issues.apache.org/jira/browse/LOG4J2-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17583200#comment-17583200 ]
ASF subversion and git services commented on LOG4J2-2557:
---------------------------------------------------------
Commit be8af7f32b53401ccbda80f3245ad21121b0439f in logging-log4j2's branch refs/heads/slf4j-2.0 from Piotr P. Karwasz
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=be8af7f32b ]
[LOG4J2-2557] Remove recursion between Logger and LoggerRepository
The `Category` class constructor should not use the static method
`LogManager.getLoggerRepository()` to find the `LoggerRepository` that
created it. The value should be injected.
> Improved printf() support.
> --------------------------
>
> Key: LOG4J2-2557
> URL: https://issues.apache.org/jira/browse/LOG4J2-2557
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.11.1
> Reporter: Robert F
> Priority: Major
> Labels: debug, error, fatal, info, log, printf, trace, warn
>
> I was excited to see log4j2 supports "printf-style messages"; however, I was disappointed to learn it was not supported by the standard logging methods.
> The standard log methods do support the "{}" formatting, but not "%" formatting. The "printf()" method is cumbersome and a longer syntax.
> Thus, I would like to see one of the following two improvements:
> 1) Have the standard log methods support both "{}" and "%" formatting.
> 2) Add methods for tracef(), debugf(), infof(), warnf(), errorf(), fatalf().
> Respectfully submitted, -RF
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)