logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Neon (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (LOG4J2-1302) log4j-slf4j-impl should provide a runtime dependency on log4j-core
Date Thu, 08 Dec 2016 17:16:58 GMT

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

Neon edited comment on LOG4J2-1302 at 12/8/16 5:16 PM:
-------------------------------------------------------

FYI, the description of the Log4j 2 SLF4J binding at https://logging.apache.org/log4j/2.0/log4j-slf4j-impl/index.html
States:
  The Log4j 2 SLF4J Binding allows applications coded to the SLF4J API to use Log4j 2 as the
implementation.

>From that statement, I interpreted "Log4j 2 *implementation*" as log4j-core.
So, it should be reword to "Log4j 2 API" and under Usage section of that page, there should
be a note that you would still need to add log4j-core.

Additionally, on that page it says: Use of the Log4j 2 SLF4J Binding (log4j-slf4j-impl-2.0.jar)
together with the SLF4J adapter (log4j-to-slf4j-2.0.jar) should never be attempted, as it
will cause events to endlessly be routed between SLF4J and Log4j 2.

aka, ONE SHOULD NEVER use log4j-slf4j-impl and log4j-slf4j-impl (which counters your future
proofing statement).


was (Author: neon):
FYI, the description of the Log4j 2 SLF4J binding at https://logging.apache.org/log4j/2.0/log4j-slf4j-impl/index.html
States:
  The Log4j 2 SLF4J Binding allows applications coded to the SLF4J API to use Log4j 2 as the
implementation.

>From that statement, I interrupted Log4j 2 implementation as log4j-core.
So, it should be reword to "Log4j 2 API" and under Usage section of that page, there should
be a note that you would still need to add log4j-core.

Additionally, on that page it says: Use of the Log4j 2 SLF4J Binding (log4j-slf4j-impl-2.0.jar)
together with the SLF4J adapter (log4j-to-slf4j-2.0.jar) should never be attempted, as it
will cause events to endlessly be routed between SLF4J and Log4j 2.

aka, ONE SHOULD NEVER use log4j-slf4j-impl and log4j-slf4j-impl (which counters your future
proofing statement).

> log4j-slf4j-impl should provide a runtime dependency on log4j-core
> ------------------------------------------------------------------
>
>                 Key: LOG4J2-1302
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1302
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: SLF4J Bridge
>            Reporter: Steve Davids
>
> After pulling in the log4j-slf4j-impl I was surprised to find out that I also needed
to add the the log4j-core dependency myself instead of the dependency pulled in automatically
from the log4j-slf4j-impl pom. I was expecting the behavior provided by slf4j-log4j12 which
does pull in the appropriate implementation to get going immediately.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message