jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jukka Zitting <jukka.zitt...@gmail.com>
Subject Re: Jackrabbit-ocm & jackrabbit-core 1.6 or 2.0
Date Thu, 10 Sep 2009 08:49:16 GMT

On Thu, Sep 10, 2009 at 9:13 AM, markao <tiantian.gao.wh@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.


Jukka Zitting

View raw message