jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-6711) Refactor IndexConstants so it can be referenced from outside oak-core
Date Tue, 26 Sep 2017 10:13:00 GMT

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

angela commented on OAK-6711:

[~stillalex], today I had another look at _o.a.j.oak.plugins.index_ package space and think
we have an odd mixture of interfaces and implementation details there, that might deserve
a somewhat bigger cleanup that just {{IndexConstants}}. Trying to sort things out I noticed
that some interfaces are even defined to be _ConsumerType_ (e.g. {{IndexInfoProvider}}). 

So, 2 things: would it make sense to refactor more out of _oak-core_ than just the {{IndexConstants}}?
If we would go that way, would it make sense to keep the _o.a.j.oak.plugins.index_ to ensure
maximal backwards compatibility and instead move the implementations left behind in _oak-core_
to a another package? I will try that in the stillalex-fork :-)

> Refactor IndexConstants so it can be referenced from outside oak-core
> ---------------------------------------------------------------------
>                 Key: OAK-6711
>                 URL: https://issues.apache.org/jira/browse/OAK-6711
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Alex Deparvu
>            Assignee: Alex Deparvu
>             Fix For: 1.7.9
> This is blocking OAK-6318, the security spi code depends on this constants class so I'd
like to move it to a different location.

This message was sent by Atlassian JIRA

View raw message