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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2016/01/25 11:06:39 UTC

[jira] [Created] (OAK-3919) Properly manage APIs / SPIs intended for public consumption

Michael Dürig created OAK-3919:
----------------------------------

             Summary: 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
            Reporter: Michael Dürig
             Fix For: 1.6


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)