Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of jukka.zitting@gmail.com
 designates 209.85.212.170 as permitted sender)
Received-SPF: pass (google.com: domain of jukka.zitting@gmail.com designates
 10.216.133.130 as permitted sender) client-ip=10.216.133.130;
MIME-Version: 1.0
In-Reply-To: 
 <CAOFYJNbhjkhYvytyJM-Z_uv5LpC7EsfpTAsSwhLzjz8UmBUxVw@mail.gmail.com>
References: 
 <CAOFYJNbhjkhYvytyJM-Z_uv5LpC7EsfpTAsSwhLzjz8UmBUxVw@mail.gmail.com>
From: Jukka Zitting <jukka.zitting@gmail.com>
Date: Tue, 6 Mar 2012 16:10:36 +0100
Message-ID: 
 <CAOFYJNa-Oj3cL321EqnAGX-n17C_ZZn5WTtg9CGHOu5Tht=_9A@mail.gmail.com>
Subject: Re: Setting up Oak (Was: [RESULT] [VOTE] Codename for the jr3
 implementation effort)
To: Jackrabbit Developers <dev@jackrabbit.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

On Tue, Mar 6, 2012 at 1:00 PM, Jukka Zitting <jukka.zitting@gmail.com> wro=
te:
> To get us started, I'll set up a basic multimodule build in oak/trunk
> along the lines of what we have in jackrabbit/trunk. As initial
> components I propose the following:
>
> =A0 =A0* oak-core, for the main codebase (incl. unit tests)
> =A0 =A0* oak-run, for a runnable jar packaging
> =A0 =A0* oak-it, for integration tests
> =A0 =A0* oak-bench, for performance tests

This is now in place (with just placeholders for most components).

> We'll start building the Oak codebase under org.apache.jackrabbit.oak
> in oak-core. To avoid having to start from scratch, I propose that we
> copy the existing MK work from org.apache.jackrabbit.mk to under
> oak-core [...]

Done in revision 1297505.

BR,

Jukka Zitting