[ https://issues.apache.org/jira/browse/SLING-10000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17341769#comment-17341769 ]
Konrad Windszus commented on SLING-10000: ----------------------------------------- Also Apache Tomcat provides a migration tool: [https://tomcat.apache.org/download-migration.cgi] (compare with https://lists.apache.org/thread.html/r31552357788a1671a7eda4d47f57ca1d30964e4150487267f689fdad%40%3Cdev.sling.apache.org%3E) > Switch to Jakarta APIs > ---------------------- > > Key: SLING-10000 > URL: https://issues.apache.org/jira/browse/SLING-10000 > Project: Sling > Issue Type: Task > Components: API > Reporter: Oliver Lietz > Priority: Major > > Java EE APIs are switching from {{javax}} to {{jakarta}}. > Jakarta Specifications: [https://jakarta.ee/specifications/] > *Candidates* > * {{javax.activation}} > * {{javax.servlet}} > * {{javax.mail}} > *Discovery* > * Should we have branch {{jakarta}} in each module which needs to switch? > * Should we use the breaking change (major version increase in most APIs) to > clean up and improve our current API or limit it to the package switch? > *Tooling* > * [Eclipse Transformer|https://github.com/eclipse/transformer] -- This message was sent by Atlassian Jira (v8.3.4#803005)