[
https://issues.apache.org/jira/browse/HTTPCLIENT-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993497#comment-15993497
]
Michael Osipov commented on HTTPCLIENT-1664:
--------------------------------------------
Log4J2 is a personal preference too, isn't it? He even did back his proposal,
this is it:
bq. Port from Apache Commons Logging to Apache Log4j 2.
What effort actually? Running {{sed}} over the source code? I could have done
this for SLF4J too two years ago. What Gary did is imposing his preferred
logging implementation which I never did. I just wanted to update the logging
facade to something new.
> 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]
