[
https://issues.apache.org/jira/browse/OAK-7024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16318601#comment-16318601
]
Julian Reschke edited comment on OAK-7024 at 1/9/18 3:31 PM:
-------------------------------------------------------------
bq. A very simple solution is to copy the class over to Oak and continue using
it (still doesn't save us from having to update all of this code though).
...and keep the package name? I wonder whether the java 11 class loader will
allow us to do that.
was (Author: reschke):
> A very simple solution is to copy the class over to Oak and continue using it
> (still doesn't save us from having to update all of this code though).
...and keep the package name? I wonder whether the java 11 class loader will
allow us to do that.
> 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
> 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
(v6.4.14#64029)
