You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Karl Wright (JIRA)" <ji...@apache.org> on 2018/01/08 12:37:00 UTC
[jira] [Commented] (HTTPCLIENT-1664) Migrate away from Commons
Logging to SLF4J
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16316222#comment-16316222 ]
Karl Wright commented on HTTPCLIENT-1664:
-----------------------------------------
My experience moving ManifoldCF from log4j to log4j2:
(1) We were forced to do it because a dependent package used it. It's idiosyncratic enough that there was no other implementation path possible.
(2) There are bindings for log4j 1.x in log4j2, but they are limited and aren't a full implementation of the API. Same deal with slf4j bindings.
(3) Any code that creates loggers or modifies them needs a complete rewrite.
(4) We simply could not get standard name=value property files to work at all. We were forced to adopt the XML logging configuration files.
> 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)
> Reporter: Michael Osipov
> Priority: Minor
> Fix For: 5.0 Beta1
>
>
> 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org