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 "angela (JIRA)" <ji...@apache.org> on 2018/05/16 16:28:00 UTC

[jira] [Commented] (OAK-7499) dependencies on 'plugins'

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

angela commented on OAK-7499:
-----------------------------

[~stillalex], [~rombert], [~mreutegg], [~mduerig] i would appreciate if you would take a look at the _OAK-7499-extractplugins.patch_. The second patch contains the followup adjustments of the security code. if we aim for separating the releases of the individual modules this would be another step to disentangle (at least the security related parts and optionally oak-jcr later on).

> dependencies on 'plugins'
> -------------------------
>
>                 Key: OAK-7499
>                 URL: https://issues.apache.org/jira/browse/OAK-7499
>             Project: Jackrabbit Oak
>          Issue Type: Sub-task
>            Reporter: angela
>            Priority: Major
>         Attachments: OAK-7499-adjustsecuritycode.patch, OAK-7499-extractplugins.patch
>
>
> subtask of OAK-7498 to drop usage of plugin classes directly from security code base:
> - extract interfaces for managers and provider services
> - replace usage of implementenations



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)