[jira] [Resolved] (OAK-6355) Usage of NodeAggregator creates cyclic dependency between oak.spi.query and oak.plugins.index.*

["angela (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OAK-6355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

angela resolved OAK-6355.
-------------------------
       Resolution: Fixed
    Fix Version/s: 1.7.3
                   1.8

[~tmueller], implemented fix as you suggested (revision 1800180). build and ITs passed.

> Usage of NodeAggregator creates cyclic dependency between oak.spi.query and oak.plugins.index.*
> -----------------------------------------------------------------------------------------------
>
>                 Key: OAK-6355
>                 URL: https://issues.apache.org/jira/browse/OAK-6355
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, indexing, query
>            Reporter: angela
>             Fix For: 1.8, 1.7.3
>
>
> As mentioned in OAK-6304 I had an another look at the dependencies of the _oak.spi.query_ packages space and found a single dependency on _oak.plugins.index.*_: 
> {{QueryIndex.FulltextQueryIndex.getNodeAggregator}} returns a {{org.apache.jackrabbit.oak.plugins.index.aggregate.NodeAggregator}}.
> As far as I could see this is the only dependency left within the _oak.spi.query_ package pointing to interfaces/classes inside _oak-core_.
> [~tmueller], would it be possible to move the {{org.apache.jackrabbit.oak.plugins.index.aggregate.NodeAggregator}} interface to some package below _oak.spi.query_ or a potential (new) _oak.spi.index_? wdyt?



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