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 "Julian Reschke (Jira)" <ji...@apache.org> on 2019/10/31 13:36:00 UTC

[jira] [Commented] (OAK-6973) Define public/internal packages

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

Julian Reschke commented on OAK-6973:
-------------------------------------

The annotation has been introduced with OAK-8707 - we still need to figure out where (else) to use it.

> Define public/internal packages
> -------------------------------
>
>                 Key: OAK-6973
>                 URL: https://issues.apache.org/jira/browse/OAK-6973
>             Project: Jackrabbit Oak
>          Issue Type: Task
>            Reporter: Marcel Reutegger
>            Priority: Major
>             Fix For: 1.20.0
>
>
> As part of the Oak modularization packages previously exported without a version will at some point have to adhere to proper semantic versioning. See also OAK-3919 and its sub-tasks.
> Since some of those packages are not meant to be used outside of Oak, there should be a mechanism to define which exported packages are public and which are considered internal. While semantic versioning rules apply to both categories, we may want to provide different guarantees/guidance to consumers of those packages. E.g. increasing the major version of a package used only by Oak has less impact compared to a major version increase of a 'public' package used by many applications.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)