[
https://issues.apache.org/jira/browse/JCR-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18080276#comment-18080276
]
Julian Reschke edited comment on JCR-4892 at 5/12/26 11:33 AM:
---------------------------------------------------------------
Looking servlet specs ([https://tomcat.apache.org/whichversion.html]):
* 4.0 (javax) - minimal Java 8 - Tomcat 9.x – _this is where we are right now
with Jackrabbit 2.22_
* 6.0 (jakarta) - minimal Java 11 - Tomcat 10.x
* 6.1 (jakarta) - minimal Java 17 - Tomcat 17.x
We can't break Jackrabbit 2.22, so a new branch would be needed.
Q: do we want to combine this with the change to Java 17
(https://issues.apache.org/jira/browse/JCR-5241), or should these be separate
steps? Is there anybody needing jakarta support who can not also use Java 17?
was (Author: reschke):
Looking servlet specs ([https://tomcat.apache.org/whichversion.html]):
* 4.0 (javax) - minimal Java 8 - Tomcat 9.x – _this is where we are right now_
* 6.0 (jakarta) - minimal Java 11 - Tomcat 10.x
* 6.1 (jakarta) - minimal Java 17 - Tomcat 17.x
We can't break Jackrabbit 2.22, so a new branch would be needed.
Q: do we want to combine this with the change to Java 17
(https://issues.apache.org/jira/browse/JCR-5241), or should these separate
steps?
Is there anybody needing jakarta support who can not also use Java 17?
> 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)
