[
https://issues.apache.org/jira/browse/JCR-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886452#comment-13886452
]
Thomas Mueller commented on JCR-3705:
-------------------------------------
> Is it a good idea to copy this classes to jackrabbit-data
I think we move classes, we don't copy them.
>The problem is the dependencies
Yes. So let's move the classes now, and if somebody comes up with a way to move
them back to jackrabbit-core let's do that (later).
> we have a package split here as the following 2 packages are also in
> jackrabbit-core
I think that's a bit problematic for OSGi, right? If yes, I would like to
rename packages as follows: in oak-core: org.apache.jackrabbit.data to
org.apache.jackrabbit.core.data; in oak-data: org.apache.jackrabbit.core to
org.apache.jackrabbit.data.core. I have to admit that's weird, but I don't see
another way.
> 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)
