[
https://issues.apache.org/jira/browse/HTTPCLIENT-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14611915#comment-14611915
]
Michael Osipov commented on HTTPCLIENT-1664:
--------------------------------------------
Commons Logging has design flaws, regardless of the missing features like value
substitution and markers, [http://stackoverflow.com/a/3223701/696632|class
loader issues]. Logback and
[http://docs.spring.io/spring/docs/current/spring-framework-reference/html/overview.html#overview-not-using-commons-logging|Spring
Framework] describe the flaws quite nice. Additionally, you have always to
swap Commons Log for another dependency commons log to slf4j.
Moreover, stable does not mean that it is wellsuited.
> 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
> Affects Versions: 5.0
> Reporter: Michael Osipov
>
> 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.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
