Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@hadoop.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
From: Jeffrey Naisbitt <jnaisbit@yahoo-inc.com>
To: "general@hadoop.apache.org" <general@hadoop.apache.org>
Date: Mon, 13 Jun 2011 10:08:58 -0700
Subject: Re: HADOOP-7106 (project unsplit) this weekend
Thread-Topic: HADOOP-7106 (project unsplit) this weekend
Thread-Index: Acwp67qow1N5lwaxSHmgr5zz32CIZwAANqZ7
Message-ID: <CA1BAE5A.790B%jnaisbit@yahoo-inc.com>
In-Reply-To: <BANLkTi=R4XV4-0formszUMymD_7h1QO4OQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.9.0.110114
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

On 6/13/11 12:01 PM, "Todd Lipcon" <todd@cloudera.com> wrote:

> On Mon, Jun 13, 2011 at 9:24 AM, Jeffrey Naisbitt
> <jnaisbit@yahoo-inc.com>wrote:
>=20
>> As you say though, I would think it should still work with three separat=
e
>> projects, so I'll just go back to that for now.  It would be nice to be
>> able
>> to build the whole thing as a single project though (since it's a single
>> repository in svn now), but that would probably take some extra work - a=
nd
>> would probably make sense in a separate Jira.
>>=20
>=20
> Yep - I think the idea is this will happen once we mavenize everything.
> Maven apparently supports the idea of "modules" - basically a recursive
> structure in which a top level pom file can build sub-poms, but the subpo=
ms
> could also continue to be built independently if necessary. I think the
> top-level pom would live in the new root.
>=20
> -Todd

I look forward to the mavenization! :)
I verified the eclipse builds are working fine for me in separate projects
and that the svn:externals work fine on yahoo-merge now.
Thanks for the quick responses and for all the other work on the "unsplit"!
-Jeff