jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Deparvu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-6318) Refactor oak.spi.security into a separate module/bundle
Date Tue, 12 Sep 2017 16:04:00 GMT

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

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

bq. but NamespaceConstants and NodeTypeConstants might not pose problems.
hmm. ok, but if you consider {{spi.security}} a different bundle, this reference means that
it would have to have a (maven) dependency on {{oak-core}}, which will introduce a cyclic
dependency, no? ({{oak-core}} should depend on this new bundle, not the other way around)

> 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
>
> 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: [~alex.parvulescu], [~rombert], [~mduerig], [~tmueller]



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

Mime
View raw message