[
https://issues.apache.org/jira/browse/HTTPCLIENT-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reopened HTTPCLIENT-1664:
----------------------------------------
Seriously, I don't see how this has been resolved. It has been migrated away
from Commons Logging to Log4J2. You now need another a shim for SLF4J. So this
issue has not been fixed anyhow.
[~garydgregory], why didn't you put any comment on this issue?
And here is the first problem with the new shim:
bq. The Log4j 2 to SLF4J Adapter allows applications coded to the Log4j 2 API
to be routed to SLF4J. Use of this adapter may cause some loss of performance
as the Log4j 2 Messages must be formatted before they can be passed to SLF4J.
With Log4j 2 as the implementation these would normally be formatted only when
they are accessed by a Filter or Appender.
> 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: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
