hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Sicker (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HTTPCLIENT-1664) Migrate away from Commons Logging to SLF4J
Date Tue, 02 May 2017 19:05:04 GMT

    [ https://issues.apache.org/jira/browse/HTTPCLIENT-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Mime
View raw message