You are viewing a plain text version of this content. The canonical link for it is here.

Posted to server-dev@james.apache.org by "Tellier Benoit (JIRA)" <se...@james.apache.org> on 2019/01/30 11:01:00 UTC

[jira] [Resolved] (JAMES-2654) Logback overrides LOG4J binding in APP

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

Tellier Benoit resolved JAMES-2654.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 3.3.0

> Logback overrides LOG4J binding in APP
> --------------------------------------
>
>                 Key: JAMES-2654
>                 URL: https://issues.apache.org/jira/browse/JAMES-2654
>             Project: James Server
>          Issue Type: Bug
>          Components: Spring Container
>    Affects Versions: master, 3.2.0
>            Reporter: Tellier Benoit
>            Priority: Major
>             Fix For: 3.3.0
>
>
> As reported by Marc Chamberlin on the user mailing list, log4J configuration is not applied in server/app
> A dependency tree analyses lead me to find the root casue: a logback dependency was leaking, and overriding the log4J one.
> Excluding the given dependencies dsolves the issues.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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