[
https://issues.apache.org/jira/browse/HTTPCLIENT-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993521#comment-15993521
]
Matt Sicker commented on HTTPCLIENT-1664:
-----------------------------------------
Log4j2 is not just a framework; it's a logging facade. In fact, log4j-api has
more features than slf4j-api (including custom Message objects, not just
strings, garbage-free mode, far more unrolled args versions of logging
messages, Java 8 lambda support, faster markers (though I believe this may have
been recently fixed in slf4j, though not like many people keep their
dependencies like that up to date), and many others), and it can log to
log4j-core, logback, or anything else you want as the API (aka the logging
facade) is separate from the implementation.
Really, when it comes down to it, log4j-api is objectively better than
slf4j-api in every way at this point. Both APIs are logging facades that can
log to whatever backend you want. Also, considering this is an Apache project,
I'd think that they'd prefer to use other Apache projects as dependencies where
possible.
> Migrate away from Commons Logging to SLF4J
> ------------------------------------------
>
> Key: HTTPCLIENT-1664
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1664
> Project: HttpComponents HttpClient
> Issue Type: Task
> Components: HttpClient (classic)
> Affects Versions: 5.0
> Reporter: Michael Osipov
> Priority: Minor
> Fix For: 5.0 Alpha2
>
>
> Commons Log is old and has several serious issue. HttpClient 5.0 should
> completely migrate away from it. SLF4J is an extremely wide support logging
> facade.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
