You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Eric Norman (Jira)" <ji...@apache.org> on 2025/08/20 17:24:00 UTC
[jira] [Resolved] (SLING-12869) migrate to Sling API 3.x and Jakarta Servlet
[ https://issues.apache.org/jira/browse/SLING-12869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Norman resolved SLING-12869.
---------------------------------
Resolution: Fixed
merged PR at: [{{c280d17}}|https://github.com/apache/sling-org-apache-sling-jcr-jackrabbit-usermanager/commit/c280d17da9be5009da70b95fb8b769cebf9b614f]
> migrate to Sling API 3.x and Jakarta Servlet
> --------------------------------------------
>
> Key: SLING-12869
> URL: https://issues.apache.org/jira/browse/SLING-12869
> Project: Sling
> Issue Type: Sub-task
> Reporter: Eric Norman
> Assignee: Eric Norman
> Priority: Major
> Fix For: JCR Jackrabbit User Manager 3.0.0
>
>
> bump bundle major version to 3.0.0
> bump minimum java version to 17
> bump slf4j-api to the 2.x version
> bump dependencies to the latest that are compatible with sling api 3.x
> migrate the javax.servlet references in non-public classes to jakarta.servlet
> break the circular test dependency on slingJcrJackrabbitAccessmanager
--
This message was sent by Atlassian Jira
(v8.20.10#820010)