[
https://issues.apache.org/jira/browse/JCR-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13884985#comment-13884985
]
Amit Jain commented on JCR-3705:
--------------------------------
Since, the files moved from the jackrabbit-core to jackrabbit-jcr-commons are
used by both the existing classes in jackrabbit-core and the DataStore
implementations which has now moved to jackrabbit-data, we need these files in
a common component.
If not jackrabbit-jcr-commons then we will need to create another component.
Changes to jackrabbit-aws-ext can be minimized by not changing the package
names for classes moved to jackrabbit-data from there. I have changed the
package names for the classes like CachingDataStore, Backend because having
oaj.ext package in jackrabbit-data did not feel right.
> 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)
