[
https://issues.apache.org/jira/browse/JCR-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17987041#comment-17987041
]
Jesper Steen Møller commented on JCR-4892:
------------------------------------------
Some projects (Tomcat, Spring, Jetty, Eclipse RAP, many others) decided to
handle the javax->jakarta rift by moving to Jakarta EE a major release, and
keep the package names and everything, but that also requires more potential
RelEng-work.
Another approach is have different artifacts relying on the different major
versions. Atlassian's Swagger Resquest Validator does this (springmvc vs
spring-webmvc artefacts, sharing version and package names).
I guess this depends on whether you are providing components relevant for web
applications, or more like shipping a full war.
Anyway, I can examine if it is possible to rename classes in e.g.
{{org.apache.jackrabbit.webdav.*}} to - say -
{{org.apache.jackrabbit.jakartaee.webdav.*}} but I think it will seem like a
really odd choice going forward, when the world moves onto Javax EE everywhere.
Please recommend package name :D
> support the jakarta.servlet package name
> ----------------------------------------
>
> Key: JCR-4892
> URL: https://issues.apache.org/jira/browse/JCR-4892
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Reporter: Julian Reschke
> Priority: Major
> Fix For: 2.24
>
> Attachments: JCR-4892_v2_project_root.patch,
> JCR-4892_v2_workspace_root.patch, JCR-4892_v3.patch, JCR-4892_v4.patch, clean
> install-Output.txt, jackrabbit-webdav-jakarta.patch, patch.txt, webapp.patch,
> webapp2.patch
>
>
> ...without breaking existing uses for now.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
