[
https://issues.apache.org/jira/browse/LOG4J2-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17419127#comment-17419127
]
Claudia Pastor Ramirez commented on LOG4J2-2978:
------------------------------------------------
[~mseele] I already a couple of projects working on Tomcat10 with log4j2. It
works with 2.14.0, but fails in things like using the context params or at
correctly closing the opened threads, but with a couple of minor workarounds we
are logging normally. I could help you if you need something for yesterday.
> 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)
