[OAK-6973] Define public/internal packages

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Epic Link: Modularisation of Oak
• Assignee: Unassigned
• Reporter: Marcel Reutegger
• Created: 22/Nov/17 15:57
• Updated: 26/May/21 14:53

Description

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.

Issue Links

• relates to: OAK-8707 Mark exported APIs that we don't want to expose with an @Internal annotation