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 2017/06/29 13:46:00 UTC
[jira] [Comment Edited] (OAK-6407) Refactor oak.spi.query into a
separate module/bundle
[ https://issues.apache.org/jira/browse/OAK-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068354#comment-16068354 ]
angela edited comment on OAK-6407 at 6/29/17 1:45 PM:
------------------------------------------------------
[~tmueller], [~stillalex], [~mduerig], may i ask you to review the proposed m12n effort for the spi.query package space? imho i will help us avoiding reintroducing the cyclic dependency chaos (that we likely ended up with inadvertently) and allow to address proper package exports as we move on.
was (Author: anchela):
[~tmueller], [~stillalex], [~mduerig], may i ask you to review the proposed m12n effort? imho i will help us avoiding reintroducing the cyclic dependency chaos (that we likely ended up with inadvertently) and allow to address proper package exports as we move on.
> Refactor oak.spi.query into a separate module/bundle
> ------------------------------------------------------
>
> Key: OAK-6407
> URL: https://issues.apache.org/jira/browse/OAK-6407
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, query
> Reporter: angela
> Assignee: angela
> Labels: modularization
> Attachments: OAK-6407.patch
>
>
> now that OAK-6304 and OAK-6355 have been resolved, i would like to suggest that we move the _o.a.j.oak.spi.query_ code base into a separate module/bundle in order to prevent the introduction of bogus cycles and odd package exports in the future.
> [~tmueller], patch will follow asap.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)