You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Oliver Lietz (Jira)" <ji...@apache.org> on 2021/01/05 10:05:00 UTC

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

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

Oliver Lietz edited comment on SLING-10000 at 1/5/21, 10:04 AM:
----------------------------------------------------------------

[~cziegeler], That's the magic I was hoping for.


was (Author: olli):
[~cziegeler], That's the magic is was hoping for.

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