[jira] [Commented] (SLING-10000) Switch to Jakarta APIs

["Carsten Ziegeler (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-10000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17258784#comment-17258784 ] 

Carsten Ziegeler commented on SLING-10000:
------------------------------------------

In general, we should only switch, if there is a real need.
I haven't looked in detail into it, but maybe https://github.com/eclipse/transformer can help here (for example by rewriting bundles using the old api to use the new api), avoiding branches and deploying two versions in parallel

> 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?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)