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 "Benoit Tellier (Jira)" <se...@james.apache.org> on 2020/03/23 03:06:00 UTC

[jira] [Closed] (JAMES-3122) Upgrade log4j for java 11 compatibility

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

Benoit Tellier closed JAMES-3122.
---------------------------------
    Fix Version/s: 3.5.0
       Resolution: Fixed

https://github.com/linagora/james-project/pull/3214 solved this.

> Upgrade log4j for java 11 compatibility
> ---------------------------------------
>
>                 Key: JAMES-3122
>                 URL: https://issues.apache.org/jira/browse/JAMES-3122
>             Project: James Server
>          Issue Type: New Feature
>          Components: Spring Container
>            Reporter: Benoit Tellier
>            Priority: Major
>             Fix For: 3.5.0
>
>
> Referencing https://www.mail-archive.com/server-user@james.apache.org/msg16315.html
> Tommy Pham:
> {code:java}
> I found the root cause of the logging for me... James 3.3 & 3.4 is still
> using log4j (version 1) that's EOL in 2015 [1] which is really broken with
> Java 9+ [2].  I'm using JDK 11 :(  I'll have to replace the log4j (v1)
> jar(s) with log4j2 add see if it works.
> [1] http://logging.apache.org/log4j/1.2/
> [2] https://blogs.apache.org/logging/entry/moving_on_to_log4j_2
> {code}
> We need to upgrade Spring packaging log4j version.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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