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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2016/03/01 10:57:18 UTC

[jira] [Comment Edited] (OAK-4039) The package o.a.j.o.query exposes multiple classes from unexported packages

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

Chetan Mehrotra edited comment on OAK-4039 at 3/1/16 9:56 AM:
--------------------------------------------------------------

bq.  In the end we already delivered 1.2 and 1.0 with such as far as I understood.

In such a case we should look into this post 1.4 unless some simpler fix can be determined. For now lets continue with the export


was (Author: chetanm):
bq.  In the end we already delivered 1.2 and 1.0 with such as far as I understood.

In such a case we should look into this post 1.4 unless some simpler fix can be determined

> The package o.a.j.o.query exposes multiple classes from unexported packages
> ---------------------------------------------------------------------------
>
>                 Key: OAK-4039
>                 URL: https://issues.apache.org/jira/browse/OAK-4039
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: Francesco Mari
>            Assignee: Thomas Mueller
>             Fix For: 1.4, 1.4.0
>
>
> Multiple exported classes in {{org.apache.jackrabbit.oak.query}} use in their public API other classes from unexported packages. {{org.apache.jackrabbit.oak.query.plan.SelectorExecutionPlan}}, {{org.apache.jackrabbit.oak.query.index.FilterImpl}}, and multiple classes from {{org.apache.jackrabbit.oak.query.ast}} are used in the public APIs of many other classes from {{org.apache.jackrabbit.oak.query}} but they are not exported by their relative packages.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)