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 "Alexander Saar (JIRA)" <ji...@apache.org> on 2016/11/10 08:21:58 UTC
[jira] [Updated] (OAK-3919) Properly manage APIs / SPIs intended
for public consumption
[ https://issues.apache.org/jira/browse/OAK-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Saar updated OAK-3919:
--------------------------------
Fix Version/s: (was: 1.6)
1.8
> 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
(v6.3.4#6332)