jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-3919) Properly manage APIs / SPIs intended for public consumption
Date Mon, 13 Nov 2017 07:44:00 GMT

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

Michael Dürig commented on OAK-3919:

[~anchela], this might have mostly been addressed by the recent modularisation effort and
/ or superseded by on of the related issues. Could you link or resolve this issue accordingly
if so?

> Properly manage APIs / SPIs intended for public consumption
> -----------------------------------------------------------
>                 Key: OAK-3919
>                 URL: https://issues.apache.org/jira/browse/OAK-3919
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Michael Dürig
>              Labels: modularization, technical_debt
>             Fix For: 1.8
> This is a follow up to OAK-3842, which removed package export declarations for all packages
that we either do not want to be used outside of Oak or that are not stable enough yet. 
> This issue is to identify those APIs and SPIs of Oak that we actually *want* to export
and to refactor those such we *can* export them. 
> Candidates that are currently used from upstream projects I know of are:
> {code}
>       org.apache.jackrabbit.oak.plugins.observation
>       org.apache.jackrabbit.oak.spi.commit
>       org.apache.jackrabbit.oak.spi.state
>       org.apache.jackrabbit.oak.commons
>       org.apache.jackrabbit.oak.plugins.index.lucene
> {code}
> I suggest to create subtask for those we want to go forward with.

This message was sent by Atlassian JIRA

View raw message