You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Michael Seele (Jira)" <ji...@apache.org> on 2021/08/27 08:52:00 UTC
[jira] [Commented] (LOG4J2-2978) Migrate to Jakarta APIs
[ https://issues.apache.org/jira/browse/LOG4J2-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405686#comment-17405686 ]
Michael Seele commented on LOG4J2-2978:
---------------------------------------
Is there any action going on right here? We are working on our first migration to tomcat 10 and log4j 2 is now unusable for us.
If i can help in any way, please let me know.
> Migrate to Jakarta APIs
> -----------------------
>
> Key: LOG4J2-2978
> URL: https://issues.apache.org/jira/browse/LOG4J2-2978
> Project: Log4j 2
> Issue Type: New Feature
> Components: Web/Servlet
> Affects Versions: 2.14.0
> Reporter: Boris Petrov
> Priority: Blocker
>
> Jakarta EE 9 is out already along with stable versions of the two most popular containers - Tomcat 10 and Jetty 11 (running on Servlet 5.0). `log4j-web` internally still uses `javax` (e.g. [here|https://github.com/apache/logging-log4j2/blob/rel/2.14.0/log4j-web/src/main/java/org/apache/logging/log4j/web/Log4jServletContainerInitializer.java#L21]) so it is incompatible with an application that runs on these two containers. It would be nice to release a new version that is compatible with them. Unfortunately a single version cannot be made compatible with both the "old" `javax` and the "new" `jakarta` namespaces so perhaps a new major one should be released.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)