[
https://issues.apache.org/jira/browse/JCR-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17987080#comment-17987080
]
Julian Reschke commented on JCR-4892:
-------------------------------------
bq. I guess this depends on whether you are providing components relevant for
web applications, or more like shipping a full war.
jackrabbit-webdav would be an example for that, right?
bq. 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.
I don't think we can avoid this if we want to be able to deploy them
side-by-side in OSGi.
bq. Please recommend package name
commons-collections handled this by just adding a number to the package name,
something like o.a.j.webdav2.
> 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)
