Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of jukka.zitting@gmail.com
 designates 209.85.220.162 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=YGiIHArnuC3HeryGT6lhC2o8UMrYeT3QHgylrdilSdxeWA3Ebvytdems03hVCunmxq
         6eITG9DC2sQDgu5b3aom4GLH8PQa383Ut6ClkqToddQ1TYvnNvYaIAtndApZ3yvbkXEJ
         4bfzPQ7HDLbtVH3fO4hYUsFEsglQIdgxvFPa0=
MIME-Version: 1.0
In-Reply-To: <510143ac0905011016x651c0d64x5e4d8815fada8500@mail.gmail.com>
References: <510143ac0905011016x651c0d64x5e4d8815fada8500@mail.gmail.com>
From: Jukka Zitting <jukka.zitting@gmail.com>
Date: Mon, 4 May 2009 10:37:15 +0200
Message-ID: <510143ac0905040137k49a02845n74e4a22bdd2fb677@mail.gmail.com>
Subject: Re: Jackrabbit core now on JCR 2.0
To: Jackrabbit Developers <dev@jackrabbit.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi,

On Fri, May 1, 2009 at 7:16 PM, Jukka Zitting <jukka.zitting@gmail.com> wrote:
> Thanks to help from Julian, we're already almost done with migrating
> all of Jackrabbit trunk to use the JCR 2.0 API. Everything compiles
> and there are only a few remaining SPI-related locking tests that
> still fail. I'll try to get them fixed over the weekend.

I didn't yet have time to figure out the cause of those issues, so I
marked them as known issues (JCR-2097) for now to make the main build
work.

With that I've just re-enabled the Jackrabbit-trunk build job in
Hudson. The trunk is again open for normal development. :-)

BR,

Jukka Zitting