hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HTTPCLIENT-1664) Migrate away from Commons Logging to SLF4J
Date Wed, 03 May 2017 12:59:04 GMT

    [ https://issues.apache.org/jira/browse/HTTPCLIENT-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994767#comment-15994767
] 

Remko Popma edited comment on HTTPCLIENT-1664 at 5/3/17 12:58 PM:
------------------------------------------------------------------

By the way, it is _not true_ that the Log4j2 API introduces the need for a "facade for a facade".
There is _zero_ difference in this respect between the Log4j2 API and SLF4J. 

Both APIs require 2 dependencies when using the native implementation, and 4 dependencies
for a non-native implementation. SLF4J and the Log4j2 API are identical in this respect.

||Required dependencies || with SLF4J as API || with log4j-api as API ||
||Logback as implementation| 2: slf4j and Logback | 4:  log4j-api, log4j-to-slf4j, slf4j,
Logback |
||Log4j 2 as implementation| 4: slf4j, log4j-slf4j-impl, log4j-api, log4j-core | 2: log4j-api
and log4j-core|

So you are [free|http://stackoverflow.com/questions/41498021/is-it-worth-to-use-slf4j-with-log4j2/41500347#41500347]
to decide purely on the [technical merits|http://stackoverflow.com/questions/41633278/can-we-use-all-features-of-log4j2-if-we-use-it-along-with-slf4j-api/41635246#41635246]
of the API itself. (And why not choose the API that allows the library to be garbage free?)


was (Author: remkop@yahoo.com):
By the way, it is _not true_ that the Log4j2 API introduces the need for a "facade for a facade".
There is _zero_ difference in this respect between the Log4j2 API and SLF4J. 

Both APIs require 2 dependencies when using the native implementation, and 4 dependencies
for a non-native implementation. SLF4J and the Log4j2 API are identical in this respect.

||Required dependencies || with SLF4J as API || with log4j-api as API ||
||Logback as implementation| 2: slf4j and Logback | 4:  log4j-api, log4j-to-slf4j, slf4j,
Logback |
||Log4j 2 as implementation| 4: slf4j, log4j-slf4j-impl, log4j-api, log4j-core | 2: log4j-api
and log4j-core|

So you are [free|http://stackoverflow.com/questions/41498021/is-it-worth-to-use-slf4j-with-log4j2/41500347#41500347]
to decide purely on the technical merits of the API itself. (And why not choose the API that
allows the library to be garbage free?)

> 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-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Mime
View raw message