[
https://issues.apache.org/jira/browse/OAK-7024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16328905#comment-16328905
]
Alex Deparvu commented on OAK-7024:
-----------------------------------
I have updated the wip branch with a cleaner solution: provide default methods
for PrincipalProvider so implementors of this code (1) can update at their
convenience and (2) can remove all references of acl.Group from their code in
preparation of the removal.
Still one thing that's bugging me is, I'm not sure I've fully managed to bypass
the need to have this code updated twice: once to the transition version and
once to the version that has no more reference to the Group interface.
Also, had a discussion with [~anchela] and we seem to agree that the new Group
interface should exist on the jackrabbit api side to cover needs for both oak
and jackrabbit, which means that JCR-4246 might to come first, or at least we'd
have to create a dedicated issue for the introduction of the new interface (and
wait for a jackrabbit release). FYI [~reschke].
Feedback appreciated!
> java.security.acl deprecated in Java 10, marked for removal in Java 11
> ----------------------------------------------------------------------
>
> Key: OAK-7024
> URL: https://issues.apache.org/jira/browse/OAK-7024
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: security
> Reporter: Julian Reschke
> Assignee: Alex Deparvu
> Priority: Major
> Fix For: 1.10
>
>
> See <https://bugs.openjdk.java.net/browse/JDK-8175094> and
> <https://bugs.openjdk.java.net/browse/JDK-8191138>.
> Need to understand how this affects public Oak APIs, and what to do with them
> on Java 11 (which will be an LTS release we probably need to support with Oak
> 1.10).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
