[
https://issues.apache.org/jira/browse/JCR-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886411#comment-13886411
]
Amit Jain commented on JCR-3705:
--------------------------------
The following packages can be moved from jackrabbit-core to jackrabbit-data.
* org.apache.jackrabbit.core
** InternalXAResource
** TransactionContext
** TransactionException
* org.apache.jackrabbit.core.config
* org.apache.jackrabbit.core.data (except GarbageCollector since, it has other
dependencies on jackrabbit-core)
* org.apache.jackrabbit.core.data.db
* org.apache.jackrabbit.core.fs
* org.apache.jackrabbit.core.fs.local
* org.apache.jackrabbit.core.util.db
Now the problem is we have a package split here as the following 2 packages are
also in jackrabbit-core
* org.apache.jackrabbit.core
* org.apache.jackrabbit.data
Is this ok? Or I should rename the packages for the classes above (which would
also involve change in the package imports in the referrers).
> Extract data store API and implementations from jackrabbit-core
> ---------------------------------------------------------------
>
> Key: JCR-3705
> URL: https://issues.apache.org/jira/browse/JCR-3705
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Jukka Zitting
> Labels: patch
> Attachments: JCR-3705.patch
>
>
> In Oak we'd like to use the Jackrabbit data stores (OAK-805). Doing so would
> currently require a direct dependency to jackrabbit-core, which is
> troublesome for various reasons.
> Since the DataStore interface and its implementations are mostly independent
> of the rest of Jackrabbit internals, it should be possible to avoid that
> dependency by moving the data store bits to some other component.
> One alternative would be to place them in jackrabbit-jcr-commons, another to
> create a separate new jackrabbit-data component for this purpose. WDYT?
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
