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

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

There are many details on this - we also should separate between updating the 
Servlet api and any other api - the servlet API is special as that is the one 
we are using in our APIs. Every other API is most likely less complicated.
Now, when it comes to the servlet API, Apache Felix Http Jetty 5.x is based on 
Jetty 11 and it supports jakarta servlet 5 and javax servlet 3. So that version 
is one way to start support Jakarta Servlet API.
But as we are using the javax servlet api in our Sling API, it is way more 
difficult. We can't simply make a major version change for all Sling API as 
this would break all current users. The Apache Felix Webconsole had a similar 
problem. There we established a *new* API using Jakarta servlet next to the 
existing one. The latest webconsole supports both APIs. But again, for Sling 
this would have a way larger impact.


> 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]
>  * [Tomcat Migration Tool for Jakarta EE 
> software|https://tomcat.apache.org/download-migration.cgi]
>  * [JetBrains IntelliJ IDEA – Automatic migration from Java EE to Jakarta 
> EE|https://blog.jetbrains.com/idea/2021/06/intellij-idea-eap-6/#automatic_migration_from_java_ee_to_jakarta_ee]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to