logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (LOG4J2-334) rename Log4j 2 SLF4J binding from log4j-slf4j-impl to slf4j-to-log4j
Date Thu, 02 Jan 2014 05:17:50 GMT

     [ https://issues.apache.org/jira/browse/LOG4J2-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ralph Goers resolved LOG4J2-334.
--------------------------------

    Resolution: Won't Fix

Closing this since it goes against the naming convention decided upon earlier and no one else
has shown interest.

> 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 was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
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