[
https://issues.apache.org/jira/browse/LOG4J2-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405811#comment-17405811
]
Volkan Yazici commented on LOG4J2-2978:
---------------------------------------
[~mseele], below outline might come handy as a first step:
# Clone [https://github.com/apache/logging-log4j2]
# Switch to {{release-2.x}} branch and make sure {{./mvnw clean verify}}
succeeds (you can also opt for the quicker {{./mvnw package -DskipTests}}
during development)
# {{git checkout -B feature/LOG4J2-2978 origin/release-2.x}}
# Copy {{log4j-web}} to {{log4j-jakarta-web}}
# Edit modules in {{/pom.xml}}
# Start hacking {{log4j-jakarta-web}}
# Update the manual in {{/src/site}}
# Update {{/src/changes/changes.xml}}
# Create a PR.
> 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)
