[SIS-596] Better encapsulation of modules internal

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.4
• Fix Version/s: 1.5
• Component/s: Coverage, Features, Metadata, Referencing, Utilities
• Assignee: Martin Desruisseaux
• Reporter: Martin Desruisseaux
• Created: 07/Mar/24 17:19
• Updated: 08/Mar/24 09:37
• Resolved: 07/Mar/24 18:22

Description

Apache SIS has some internal packages not intended to appear in public API. Some internal packages are read by other SIS modules. Those packages must be declared by qualified exports. In order to avoid exporting more than intended, the following convention can be applied:

• org.apache.sis.*.internal are strictly internal to the module. Those packages should not be exported at all, not even as qualified exports.
• org.apache.sis.*.privy are internal packages shared by other modules. "Privy" means "something that is known or understood by only a select few individuals". The "individuals" here are the SIS modules.

This task is about moving some (not all) classes from internal to privy packages, depending on whether they are used by other modules. The goal is to improve encapsulation by avoiding to export some classes that are internal mechanic even from the point of view of other SIS modules.

Issue Links

• depends upon: SIS-587 Rename internal packages