[
https://issues.apache.org/jira/browse/SLING-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-372.
-----------------------------------
Resolution: Fixed
This change has been implemented. So I close this issue.
> Do not export jackrabbit core classes from jcr/jackrabbit-server module
> -----------------------------------------------------------------------
>
> Key: SLING-372
> URL: https://issues.apache.org/jira/browse/SLING-372
> Project: Sling
> Issue Type: Improvement
> Components: Repository
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> The jcr/jackrabbit-server module currently exports (almost) all classes from
> the jackrabbit-core library for use by other bundles, mostly to support
> extension point implementation.
> This is probably not the best of all ideas, because it opens up the internal
> implementation of jackrabbit core. If the need arises to implement such
> extension points in foreign modules, the jackrabbit core should be modified
> to clearly separate such extension point interfaces and internal
> implementations.
> So, the jcr/jackrabbit-server modules should not export anything for now.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
