[
https://issues.apache.org/jira/browse/JCR-5225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18055167#comment-18055167
]
Julian Reschke commented on JCR-5225:
-------------------------------------
Potential approaches I can think of:
- fork the API somewhere else: would have the same impact as a move to Jakarta,
and, in addition, a copyright problem
- provide a minimal JAR that only contains that class; that would solve the
problem (I think), but would be problematic wrt copyright as well
> pending removal of java.security.AccessControlException will break JCR API
> --------------------------------------------------------------------------
>
> Key: JCR-5225
> URL: https://issues.apache.org/jira/browse/JCR-5225
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: JCR API
> Reporter: Julian Reschke
> Priority: Critical
>
> {{java.security.AccessControlException}} is deprecated "for removal" any
> might disappear in the next LTS release (Java 29, est 2027) (see
> https://docs.oracle.com/en/java/javase/25/docs/api/java.base/java/security/AccessControlException.html)
> This will break the JCRP API:
> https://developer.adobe.com/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/javax/jcr/Session.html#checkPermission(java.lang.String,java.lang.String)
> The JCR API de facto is frozen:
> - it's not part of J2EE, so does not have a home at Jakarta (not even
> considering the impact of the package name change)
> - an actual revision "in place" would require a new JSR and expert group
> (unlikely, but I'd like to be proven otherwise)
> FWIW, [email protected] is where this can be discussed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
