You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by markao <ti...@nikoyo.com.cn> on 2009/09/10 09:13:22 UTC
Jackrabbit-ocm & jackrabbit-core 1.6 or 2.0
I see that the OCM component was moved outside Jackrabbit trunk along with
other
components that depend only on the standard JCR API. The lastest
jackrabbit-ocm version is 1.5.3. It depends on jackrabbit-core-1.5.0(I fount
that in the pom.xml of jackrabbit-ocm-1.5.3).
<dependency>
<groupId>org.apache.jackrabbit</groupId>
<artifactId>jackrabbit-core</artifactId>
<version>1.5.0</version>
<scope>test</scope>
</dependency>
So I want to know whether it can work with jackrabbit-core-1.6.0. Also if
jackrabbit upgrade to 2.0, the ocm component will still work fine?
Thank you~
--
View this message in context: http://www.nabble.com/Jackrabbit-ocm---jackrabbit-core-1.6-or-2.0-tp25378452p25378452.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
Re: Jackrabbit-ocm & jackrabbit-core 1.6 or 2.0
Posted by markao <ti...@nikoyo.com.cn>.
Thank u very much.
Jukka Zitting wrote:
>
> Hi,
>
> On Thu, Sep 10, 2009 at 9:13 AM, markao <ti...@nikoyo.com.cn>
> wrote:
>> I see that the OCM component was moved outside Jackrabbit trunk along
>> with
>> other components that depend only on the standard JCR API. The lastest
>> jackrabbit-ocm version is 1.5.3. It depends on jackrabbit-core-1.5.0(I
>> fount
>> that in the pom.xml of jackrabbit-ocm-1.5.3).
>>
>> <dependency>
>> <groupId>org.apache.jackrabbit</groupId>
>> <artifactId>jackrabbit-core</artifactId>
>> <version>1.5.0</version>
>> <scope>test</scope>
>> </dependency>
>
> It's a test dependency. In normal use OCM depends only on the JCR API
> so you can use it with any version of Jackrabbit. It even works with
> other JCR implementations.
>
>> So I want to know whether it can work with jackrabbit-core-1.6.0. Also if
>> jackrabbit upgrade to 2.0, the ocm component will still work fine?
>
> Yes. JCR 2.0 is backwards compatible, so JCR 1.0 clients like OCM 1.x
> should work without any changes.
>
> BR,
>
> Jukka Zitting
>
>
--
View this message in context: http://www.nabble.com/Jackrabbit-ocm---jackrabbit-core-1.6-or-2.0-tp25378452p25379904.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
Re: Jackrabbit-ocm & jackrabbit-core 1.6 or 2.0
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Thu, Sep 10, 2009 at 9:13 AM, markao <ti...@nikoyo.com.cn> wrote:
> I see that the OCM component was moved outside Jackrabbit trunk along with
> other components that depend only on the standard JCR API. The lastest
> jackrabbit-ocm version is 1.5.3. It depends on jackrabbit-core-1.5.0(I fount
> that in the pom.xml of jackrabbit-ocm-1.5.3).
>
> <dependency>
> <groupId>org.apache.jackrabbit</groupId>
> <artifactId>jackrabbit-core</artifactId>
> <version>1.5.0</version>
> <scope>test</scope>
> </dependency>
It's a test dependency. In normal use OCM depends only on the JCR API
so you can use it with any version of Jackrabbit. It even works with
other JCR implementations.
> So I want to know whether it can work with jackrabbit-core-1.6.0. Also if
> jackrabbit upgrade to 2.0, the ocm component will still work fine?
Yes. JCR 2.0 is backwards compatible, so JCR 1.0 clients like OCM 1.x
should work without any changes.
BR,
Jukka Zitting