[
https://issues.apache.org/jira/browse/LOG4J2-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727805#comment-13727805
]
Ralph Goers commented on LOG4J2-334:
------------------------------------
This goes against the decision that was made several months ago to have all
artifacts start with log4j-
> rename Log4j 2 SLF4J binding from log4j-slf4j-impl to slf4j-to-log4j
> --------------------------------------------------------------------
>
> Key: LOG4J2-334
> URL: https://issues.apache.org/jira/browse/LOG4J2-334
> Project: Log4j 2
> Issue Type: Improvement
> Components: JCL Bridge
> Affects Versions: 2.0-beta8
> Reporter: Hervé Boutemy
> Priority: Critical
>
> while working on LOG4J2-332, I read the good following advice:
> bq. Use of the 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.
> but compare with
> bq. Use of the SLF4J binding (slf4j-to-log4j-2.0.jar) together with the SLF4J
> adapter (log4j-to-slf4j-2.0.jar) should never be attempted
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
