[SLING-10000] Switch to Jakarta APIs

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: API
• Assignee: Unassigned
• Reporter: Oliver Lietz
• Created: 12/Dec/20 04:06
• Updated: 25/Sep/23 15:14

Description

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
• Tomcat Migration Tool for Jakarta EE software
• JetBrains IntelliJ IDEA – Automatic migration from Java EE to Jakarta EE

Issue Links

• is related to: FELIX-6247 Jakarta servlet API support by Felix HttpService
• is related to: JCR-4892 support the jakarta.servlet package name
• is related to: FELIX-6574 Update to OSGi Servlet Whiteboard specification
• mentioned in: Page Loading...

Sub-Tasks

• Switch to Jakarta Mail and Activation APIs: Closed
• Support Jakarta Servlet APIs: Resolved