[
https://issues.apache.org/jira/browse/LOG4J2-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314079#comment-15314079
]
Remko Popma commented on LOG4J2-1404:
-------------------------------------
No problem! :-)
Personally I advise everybody to stop using SLF4J and use the Log4j2 API
instead. It lets you use modern and powerful new features. If you change your
mind later you can always fall back with log4j-to-slf4j.
> log4j-slf4j-impl 2.6 is warning
> --------------------------------
>
> Key: LOG4J2-1404
> URL: https://issues.apache.org/jira/browse/LOG4J2-1404
> Project: Log4j 2
> Issue Type: Bug
> Components: SLF4J Bridge
> Affects Versions: 2.6
> Environment: Log4j 2.6 slf4j 1.7.13-21
> Reporter: yuedaxia
> Fix For: 2.6.1
>
>
> when use log4j 2 2.6 ,
> some class like private static final Logger log =
> LoggerFactory.getLogger(RestDispatcherServlet .class);
> has warning :
> WARN The Logger com.gentlesoft.framework.RestDispatcherServlet was created
> with the message factory
> org.apache.logging.log4j.spi.MessageFactory2Adapter@31bd1cd3 and is now
> requested with a null message factory (defaults to
> org.apache.logging.log4j.message.ParameterizedMessageFactory), which may
> create log events with unexpected formatting.
> but some class no warning.
> log4j 2.5 no this problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
