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/07/19 18:50:00 UTC
[jira] [Updated] (SLING-10000) Switch to Jakarta APIs
[ https://issues.apache.org/jira/browse/SLING-10000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver Lietz updated SLING-10000:
---------------------------------
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|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]
was:
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]
> 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.3.4#803005)