[
https://issues.apache.org/jira/browse/OAK-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amit Jain updated OAK-2932:
---------------------------
Fix Version/s: (was: 1.3.5)
1.3.6
> Limit the scope of exported packages
> ------------------------------------
>
> Key: OAK-2932
> URL: https://issues.apache.org/jira/browse/OAK-2932
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Reporter: Michael Dürig
> Assignee: Francesco Mari
> Labels: modularization, osgi, technical_debt
> Fix For: 1.3.6
>
>
> Oak currently exports *a lot* of packages even though those are only used by
> Oak itself. We should probably leverage OSGi subsystems here and only export
> the bare minimum to the outside world. This will simplify evolution of Oak
> internal APIs as with the current approach changes to such APIs always leak
> to the outside world.
> That is, we should have an Oak OSGi sub-system as an deployment option.
> Clients would then only need to deploy that into their OSGi container and
> would only see APIs actually meant to be exported for everyone (like e.g. the
> JCR API). At the same time Oak could go on leveraging OSGi inside this
> subsystem.
> cc [~bosschaert] as you introduced us to this idea.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
