[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=15995280#comment-15995280 ] Remko Popma commented on HTTPCLIENT-1664: - Log4j-core requires log4j-api, just like Logback does not work without SLF4J in the classpath. > 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
[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=15995185#comment-15995185 ] Remko Popma commented on HTTPCLIENT-1664: - You also use a facade for a facade if you do SLF4J => log4j-slf4j-impl => log4j-api => log4j-core. SLF4J has the same problem. > 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
[jira] [Comment Edited] (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=15994767#comment-15994767 ] Remko Popma edited comment on HTTPCLIENT-1664 at 5/3/17 1:03 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 log4j-api as API || with SLF4J as API || ||Log4j 2 as implementation| 2: log4j-api and log4j-core| 4: slf4j, log4j-slf4j-impl, log4j-api, log4j-core | ||Logback as implementation| 4: log4j-api, log4j-to-slf4j, slf4j, Logback | 2: slf4j and Logback | 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: rem...@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|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?) > 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
[jira] [Comment Edited] (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=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: rem...@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-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[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=15994767#comment-15994767 ] Remko Popma commented on HTTPCLIENT-1664: - 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-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Comment Edited] (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=15994091#comment-15994091 ] Remko Popma edited comment on HTTPCLIENT-1664 at 5/3/17 12:22 AM: -- I'm of the [opinion|http://stackoverflow.com/a/41635246/1446916] that is SLF4J showing its age. (I contribute to Log4j2 and I'm biased.) Key advantage the Log4j2 API is that it allows garbage free logging. Libraries like HttpClient should aim to be garbage free (at least during steady state operation). It would not make sense to pick a logging API that prevents that. was (Author: rem...@yahoo.com): I'm of the [opinion|http://stackoverflow.com/a/41635246/1446916] that is SLF4J showing its age. (I contribute to Log4j2 and I'm likely biased.) Key advantage the Log4j2 API is that it allows garbage free logging. Libraries like HttpClient should aim to be garbage free (at least during steady state operation). It would not make sense to pick a logging API that prevents that. > 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
[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=15994091#comment-15994091 ] Remko Popma commented on HTTPCLIENT-1664: - I'm of the [opinion|http://stackoverflow.com/a/41635246/1446916] that is SLF4J showing its age. (I contribute to Log4j2 and I'm likely biased.) Key advantage the Log4j2 API is that it allows garbage free logging. Libraries like HttpClient should aim to be garbage free (at least during steady state operation). It would not make sense to pick a logging API that prevents that. > 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
