[
https://issues.apache.org/jira/browse/JCR-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18078840#comment-18078840
]
Julian Reschke commented on JCR-4892:
-------------------------------------
Hi Claus.
I realize that we are (I am) late with this.
I did some research (that is asked AIs) to undestand other options (such as
just copying the code and ensuring it keeps in sync, the IntelliJ adapter
library etc), but at the end of the day, we should just listen to people who
already did it.
Yes, the jakarta version nowadays is more important, thus the javax version
would become a 2nd class citizen (for compat only).
The best way forward is definitively to have a PR that we can iterate on. Any
chance that you could start with that?
Also, versioning: if we get this into "trunk" (so it would go into beta release
only so far), would that help? We could then include it into Jackrabbit 2.24
while deprecating the javax version.
Q: do we need to have this for < Java 17? (because we might want to switch to
that soon)
> 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
> Assignee: 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, experiment.diff, 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)
