[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=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=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] [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=15994624#comment-15994624 ] Dominik Psenner edited comment on HTTPCLIENT-1664 at 5/3/17 10:17 AM: -- Please list formal (technical) requirements that are unmet with the current implementation so that they can be addressed. was (Author: nachbarslumpi): Please list formal requirements that are unmet with the current implementation so that they can be addressed. > 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=15994605#comment-15994605 ] Michael Osipov edited comment on HTTPCLIENT-1664 at 5/3/17 10:14 AM: - Excuse me? I have chosen one, no one wanted it. I also wrote I do not intend to write on paper on that. Seems like it was never needed, I should have done the commit as Gary did within a day. Period. It pretty much seems like I have a different understanding of a clear concensus than you guys. was (Author: michael-o): Excuse me? I have chosen one, no one wanted it. I also wrote I do not intend to write on paper on that. Seems like it was never needed, I should have done the commit as Gary did within a day. Period. It pretty much seems like a have a different opion on a clear concensus than you guys. > 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=15994605#comment-15994605 ] Michael Osipov edited comment on HTTPCLIENT-1664 at 5/3/17 10:06 AM: - Excuse me? I have chosen one, no one wanted it. I also wrote I do not intend to write on paper on that. Seems like it was never needed, I should have done the commit as Gary did within a day. Period. It pretty much seems like a have a different opion on a clear concensus than you guys. was (Author: michael-o): Excuse me? I have chosen one, no one wanted it. I also wrote I do not intend to write on paper on that. Seems like it was never needed, I should have done the commit as Gary did within a day. Period. > 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=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] [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=15993522#comment-15993522 ] Michael Osipov edited comment on HTTPCLIENT-1664 at 5/2/17 7:11 PM: Philippe, it's the other way around. I made a proposal, held a discussion, devs disagreed, I didn't go futher and let the bug sleep. Now, another dev files an issue for his tool of choice, a day later the code is committed. No time for review or any further discussion. This is not equal treatment. was (Author: michael-o): Philippe, it's the other way around. I made a propopal, held a discussion, devs disagreed, I didn't go futher and let the bug sleep. Now, another dev files an issue for his tool of choice, a day later the code is committed. No time for review or any further discussion. This is not equal treatment. > 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=15993521#comment-15993521 ] Matt Sicker edited comment on HTTPCLIENT-1664 at 5/2/17 7:04 PM: - Log4j2 is not just a framework; it's a logging facade. In fact, log4j-api has more features than slf4j-api (including custom Message objects, not just strings, garbage-free mode, far more unrolled args versions of logging messages, Java 8 lambda support, faster markers (though I believe this may have been recently fixed in slf4j, though not like many people keep their dependencies like that up to date), and many others), and it can log to log4j-core, logback, or anything else you want as the API (aka the logging facade) is separate from the implementation. Really, when it comes down to it, log4j-api is objectively better than slf4j-api in every way at this point. Both APIs are logging facades that can log to whatever backend you want. Also, considering this is an Apache project, I'd think that they'd prefer to use other Apache projects as dependencies where possible. Edit: let me also add that please do not use JUL at any cost. Not only is configuring it to redirect to your actual logging framework needlessly difficult, it is tremendously slow and affects the performance of your library. was (Author: jvz): Log4j2 is not just a framework; it's a logging facade. In fact, log4j-api has more features than slf4j-api (including custom Message objects, not just strings, garbage-free mode, far more unrolled args versions of logging messages, Java 8 lambda support, faster markers (though I believe this may have been recently fixed in slf4j, though not like many people keep their dependencies like that up to date), and many others), and it can log to log4j-core, logback, or anything else you want as the API (aka the logging facade) is separate from the implementation. Really, when it comes down to it, log4j-api is objectively better than slf4j-api in every way at this point. Both APIs are logging facades that can log to whatever backend you want. Also, considering this is an Apache project, I'd think that they'd prefer to use other Apache projects as dependencies where possible. > 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=15993497#comment-15993497
]
Michael Osipov edited comment on HTTPCLIENT-1664 at 5/2/17 6:52 PM:
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.
and a day later, the issue was fixed w/o further discussion.
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 modern.
was (Author: michael-o):
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 modern.
> 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=15993497#comment-15993497
]
Michael Osipov edited comment on HTTPCLIENT-1664 at 5/2/17 6:50 PM:
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 modern.
was (Author: michael-o):
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: 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=15993155#comment-15993155 ] Michael Osipov edited comment on HTTPCLIENT-1664 at 5/2/17 4:08 PM: Seriously, I don't see how this has been resolved. It has been migrated away from Commons Logging to Log4J2. You now need another a shim for SLF4J. So this issue has not been fixed anyhow. [~garydgregory], why didn't you put any comment on this issue? And here is the first problem with the new shim: bq. The Log4j 2 to SLF4J Adapter allows applications coded to the Log4j 2 API to be routed to SLF4J. Use of this adapter may cause some loss of performance as the Log4j 2 Messages must be formatted before they can be passed to SLF4J. With Log4j 2 as the implementation these would normally be formatted only when they are accessed by a Filter or Appender. What do we actually gain then? Nothing, Commons Logging did very much the same. was (Author: michael-o): Seriously, I don't see how this has been resolved. It has been migrated away from Commons Logging to Log4J2. You now need another a shim for SLF4J. So this issue has not been fixed anyhow. [~garydgregory], why didn't you put any comment on this issue? And here is the first problem with the new shim: bq. The Log4j 2 to SLF4J Adapter allows applications coded to the Log4j 2 API to be routed to SLF4J. Use of this adapter may cause some loss of performance as the Log4j 2 Messages must be formatted before they can be passed to SLF4J. With Log4j 2 as the implementation these would normally be formatted only when they are accessed by a Filter or Appender. > 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-tabpanelfocusedCommentId=14613082#comment-14613082
]
Michael Osipov edited comment on HTTPCLIENT-1664 at 7/3/15 10:03 AM:
-
At least {}-placeholders and markers.
was (Author: michael-o):
At least {{{}-placeholders}} and markers.
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: 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-tabpanelfocusedCommentId=14613020#comment-14613020 ] Michael Osipov edited comment on HTTPCLIENT-1664 at 7/3/15 9:01 AM: [~garydgregory], you are comparing apples with oranges. Log4J is a logging framework whereas SLF4J is a logging facade. was (Author: michael-o): You are comparing apples with oranges. Log4J is a logging framework whereas SLF4J is a logging facade. 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: 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-tabpanelfocusedCommentId=14611915#comment-14611915 ] Michael Osipov edited comment on HTTPCLIENT-1664 at 7/2/15 12:57 PM: - Commons Logging has design flaws, regardless of the missing features like value substitution and markers, [class loader issues|http://stackoverflow.com/a/3223701/696632]. Logback and [Spring Framework|http://docs.spring.io/spring/docs/current/spring-framework-reference/html/overview.html#overview-not-using-commons-logging] 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. was (Author: michael-o): 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: 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-tabpanelfocusedCommentId=14612009#comment-14612009 ] Michael Osipov edited comment on HTTPCLIENT-1664 at 7/2/15 2:24 PM: The rest is still not available and the docs still refer to Tomcat 5.5 which is dead. was (Author: michael-o): The rest is still not available. 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: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
