You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Alex Deparvu (JIRA)" <ji...@apache.org> on 2017/10/02 14:11:00 UTC

[jira] [Commented] (OAK-6318) Refactor oak.spi.security into a separate module/bundle

    [ https://issues.apache.org/jira/browse/OAK-6318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16188084#comment-16188084 ] 

Alex Deparvu commented on OAK-6318:
-----------------------------------

I had to rollback the commit due to failures on various platforms (some builds were passing, some were not) so the tree package export thing does not look stable enough to be used.

> Refactor oak.spi.security into a separate module/bundle
> -------------------------------------------------------
>
>                 Key: OAK-6318
>                 URL: https://issues.apache.org/jira/browse/OAK-6318
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: core, security
>            Reporter: angela
>            Assignee: angela
>         Attachments: PropInfo.patch
>
>
> In the light of the modularization effort it would IMHO make a lot of sense to refactor _oak.spi.security.*_ into a separate module/bundle that could be release independent of _oak-core_.
> As far as I could see so far this is currently not easily doable due to the dependency of {{oak.spi.security.*}} on {{oak.plugins.tree}}, which in turn relies on {{o.a.j.oak.query.QueryEngineSettings}} and other oak-core internals (see also OAK-6304). Most likely this issue would therefore require a complete review (and possibly a split) of  the {{oak.plugins.tree}} package space which contains a mixture of utilities and 'API' (like e.g. {{TreeContext}} and {{TreeLocation}})... will open a separate issue for this linking to this one.
> cc: [~stillalex], [~rombert], [~mduerig], [~tmueller]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)