[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=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-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=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=15995076#comment-15995076 ] Michael Osipov commented on HTTPCLIENT-1664: You do use a facade for a facade if you do Log4J2 => SLF4J => SLF4J Simple or Logback. > 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=15994640#comment-15994640 ] Michael Osipov commented on HTTPCLIENT-1664: Wrong approach. If someone considers Log4J2 is a better solution, he should argue the benefits of and linking to this ticket as superseded. > 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=15994624#comment-15994624 ] Dominik Psenner commented on HTTPCLIENT-1664: - 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] [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=15994605#comment-15994605 ] Michael Osipov commented on HTTPCLIENT-1664: 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] [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=15994600#comment-15994600 ] Oleg Kalnichevski commented on HTTPCLIENT-1664: --- bq. So you are implying that people gave their consent on the change? If so, I don't see it. There was never a consensus on the matter of one true logging facade and there will never be. All we can do is to choose a good one and stick to that choice. You were asked to do some work towards that goal but you refused. Oleg > 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=15994576#comment-15994576 ] Michael Osipov commented on HTTPCLIENT-1664: No, it should not because it proposed using SLF4J. We have already a logging facade in place, namely Commons Logging. > 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=15994567#comment-15994567 ] Dominik Psenner commented on HTTPCLIENT-1664: - To me this issues' title should read as "Replace Commons Logging with a logging facade api" because this issue is essentially about that. Both slf4j and log4j2-api are good choices. So if either choice has been implemented, it is good for the HTTPCLIENT project. > 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=15994535#comment-15994535 ] Michael Osipov commented on HTTPCLIENT-1664: So you are implying that people gave their consent on the change? If so, I don't see it. > 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=15994520#comment-15994520 ] Oleg Kalnichevski commented on HTTPCLIENT-1664: --- bq. That is not absolutely not true. It is all in this very JIRA ticket. Oleg > 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=15994488#comment-15994488 ] Michael Osipov commented on HTTPCLIENT-1664: bq. You just flat out refused to put work into this issue. That is not absolutely not true. You and others did not want to change. See comments back in July 2015. I backed off. What did you expect me to do? Go against the concensus? That's ridiculous. Please show me the discussion for Log4J2. There is none, the ticket is barely filled with information. All I see is this: http://www.mail-archive.com/dev@hc.apache.org/msg17847.html No everyone needs a facade for a facade. People will express the same concerns as done in [this answer|http://stackoverflow.com/a/41500347/696632]. > 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=15994341#comment-15994341 ] Michael Osipov commented on HTTPCLIENT-1664: Remko, even if it is better. It still does not rectify to go ahead w/o a proper proposal and a discussion. I haven't seen both. > 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=15993542#comment-15993542 ] Michael Osipov commented on HTTPCLIENT-1664: No, I didn't and there was no response to Gary's statement, thus no consent. Anyway, I expect someone to check the bug list first before creating new one. Especially because Oleg raised the issue on the dev list proposing the same as I did a year ago, but I was downvoted back then. > 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=15993532#comment-15993532 ] Philippe Mouawad commented on HTTPCLIENT-1664: -- [~michael-o], did you see this thread ?: https://www.mail-archive.com/dev@hc.apache.org/msg16748.html Maybe I missed something, but I remember that for this migration it was done after some long discussion and Gary worked on it some days. > 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=15993522#comment-15993522 ] Michael Osipov commented on HTTPCLIENT-1664: 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] [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=15993511#comment-15993511 ] Philippe Mouawad commented on HTTPCLIENT-1664: -- Hello, At [~michael-o], I don't think it is a good way to argument by depreciating others work. I don't think what was done is just a matter of sed, and even if it had been, it is work which surely took hours. Besides, AFAIK, Gary contributes other work on the project and on other apache projects, such contribution probably done on his personal work SHALL NOT be attacked this way, that's not Apache philosophy IMU and not kind. I am sure you wouldn't appreciate such consideration of your work on other Apache project, I wouldn't appreciate it on my work neither. Let's be kind with each other and world will be better. Regards Philippe > 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=15993497#comment-15993497
]
Michael Osipov commented on HTTPCLIENT-1664:
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] [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=15993463#comment-15993463 ] Oleg Kalnichevski commented on HTTPCLIENT-1664: --- bq. Seriously, I don't see how this has been resolved. [~michael-o] I am not sure what kind of resolution you expect. You have been asked to back your proposal with something other than your personal preferences but you refused. I do not necessarily agree with [~garydgregory] but at the very least he was willing to put effort into it and I respect that. bq. Use of this adapter may cause some loss of performance This sounds like a problem with the SLF4J adapter and not the Log4j 2 API per se. Oleg > 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-tabpanelfocusedCommentId=14612954#comment-14612954 ] Gary Gregory commented on HTTPCLIENT-1664: -- I vote with bias for log4j 2 (I am a committer and PMC member). The project is actively maintained and is richer in feature than slf4j imo. 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] [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-tabpanelfocusedCommentId=14612965#comment-14612965 ] Oleg Kalnichevski commented on HTTPCLIENT-1664: --- @Michael: you might want to search the archives of HC user list for threads with a title 'Logging Wars'. We had many ;) Oleg 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] [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-tabpanelfocusedCommentId=14612970#comment-14612970 ] Sebb commented on HTTPCLIENT-1664: -- Note that Commons Logging does support formatters via configuration of the underlying logging system. Even SimpleLog [1] allows configuration of the date format. Other providers supported by CL allow more sophisticated configuration. [1] http://commons.apache.org/proper/commons-logging/guide.html#A_Quick_Guide_To_Simple_Log 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] [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-tabpanelfocusedCommentId=14613023#comment-14613023 ] Michael Osipov commented on HTTPCLIENT-1664: This is not what I am talking about. 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] [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-tabpanelfocusedCommentId=14612930#comment-14612930 ] Michael Osipov commented on HTTPCLIENT-1664: The content ist still horribly out of date. Moreover, no markers, nor formatters. 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] [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-tabpanelfocusedCommentId=14612963#comment-14612963 ] Oleg Kalnichevski commented on HTTPCLIENT-1664: --- I am a happy user of Log4j2 and can recommend it wholeheartedly, but HttpClient should not be using it directly. Oleg 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] [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-tabpanelfocusedCommentId=14613030#comment-14613030 ] Michael Osipov commented on HTTPCLIENT-1664: My intention is not a flame war, this is simply a waste of time. I just want to bring 5.0 to a new level with good contributions. 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] [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-tabpanelfocusedCommentId=14613054#comment-14613054 ] Sebb commented on HTTPCLIENT-1664: -- +1 to Oleg's suggestion. If you decide to take that approach, it would help to start with a Wiki page which documents the proposal(s). Once the details, pros and cons of each approach have been documented, then go for a vote. 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] [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-tabpanelfocusedCommentId=14613085#comment-14613085 ] Michael Osipov commented on HTTPCLIENT-1664: I do not intend to write a paper on 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 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] [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-tabpanelfocusedCommentId=14613082#comment-14613082
]
Michael Osipov commented on HTTPCLIENT-1664:
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] [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-tabpanelfocusedCommentId=14613083#comment-14613083
]
Michael Osipov commented on HTTPCLIENT-1664:
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] [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-tabpanelfocusedCommentId=14613037#comment-14613037 ] Oleg Kalnichevski commented on HTTPCLIENT-1664: --- @Michael: We'll never agree on one true logging framework. I have given up on that many moons ago. We ran a poll in 2008 and decided to keep Commons Logging at that time. http://markmail.org/message/f6byueamoq6h5bv2 http://markmail.org/message/wknlpebmewq2kdqm If you want this change to happen, please consider starting a similar poll on the matter at httpclient-us...@hc.apache.org. This issue cannot be resolved based on technical merits of alternative logging frameworks alone. What we could do though is to go with an option backed by a substantial majority. Oleg 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] [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-tabpanelfocusedCommentId=14613088#comment-14613088 ] Michael Osipov commented on HTTPCLIENT-1664: A vote sounds fine but I highly doubt that the response will be higher than before. 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] [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-tabpanelfocusedCommentId=14611822#comment-14611822 ] Sebb commented on HTTPCLIENT-1664: -- 1) Commons Logging has not been updated in a long while because it is very stable; age is irrelevant here. 2) What are the serious issues to which you refer? 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] [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-tabpanelfocusedCommentId=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: 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-tabpanelfocusedCommentId=14611983#comment-14611983 ] Sebb commented on HTTPCLIENT-1664: -- The classloader issues are dealt with here: http://wiki.apache.org/commons/Commons_Logging_FUD 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] [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-tabpanelfocusedCommentId=14612009#comment-14612009 ] Michael Osipov commented on HTTPCLIENT-1664: 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
[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-tabpanelfocusedCommentId=14612863#comment-14612863 ] Sebb commented on HTTPCLIENT-1664: -- I've updated the Tomcat reference in the Wiki; from version 6 it uses a different approach which avoids the classloader issue. Tomcat still uses the Commons Logging code, so it clearly works for them. However the faulty Tomcat 5.5 implementation continues to cloud people's view of Commons Logging. A bad reputation is very hard to dispel. 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
