Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Tue, 3 Dec 2013 13:36:45 +0000 (UTC)
From: =?utf-8?Q?Claus_K=C3=B6ll_=28JIRA=29?= <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <JIRA.12682365.1386071868381.61442.1386077805383@arcas>
In-Reply-To: <JIRA.12682365.1386071868381@arcas>
References: <JIRA.12682365.1386071868381@arcas>
Subject: [jira] [Commented] (JCR-3705) Extract data store API and
 implementations from jackrabbit-core
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/JCR-3705?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D138376=
84#comment-13837684 ]=20

Claus K=C3=B6ll commented on JCR-3705:
---------------------------------

Sounds good. it would also be great if we have the multidatastore in oak

> 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
>
> In Oak we'd like to use the Jackrabbit data stores (OAK-805). Doing so wo=
uld currently require a direct dependency to jackrabbit-core, which is trou=
blesome for various reasons.
> Since the DataStore interface and its implementations are mostly independ=
ent of the rest of Jackrabbit internals, it should be possible to avoid tha=
t 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#6144)