Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@hadoop.apache.org
Received-SPF: unknown (nike.apache.org: error in processing during lookup of
 jrottinghuis@ebay.com)
DomainKey-Signature: s=corp; d=ebay.com; c=nofws; q=dns;
  h=X-EBay-Corp:X-IronPort-AV:Received:Received:From:To:Date:
   Subject:Thread-Topic:Thread-Index:Message-ID:References:
   In-Reply-To:Accept-Language:Content-Language:
   X-MS-Has-Attach:X-MS-TNEF-Correlator:acceptlanguage:
   x-ems-proccessed:x-ems-stamp:Content-Type:
   Content-Transfer-Encoding:MIME-Version:X-CFilter;
  b=t3AKMRpiRQSwkZf00uCjbDyZWUZs+M7SQc/DYL3wJzaDq0rhdpbgUHNq
   gFnoraKDrf27SfUq6WPSFcLmZOgn9cPU7D1B8t2gkM8AwS0so+hMc1LbM
   KdnhvY9bT3JV+GV;
From: "Rottinghuis, Joep" <jrottinghuis@ebay.com>
To: "general@hadoop.apache.org" <general@hadoop.apache.org>
Date: Fri, 29 Jul 2011 17:11:16 -0700
Subject: RE: follow up Hadoop mavenization work
Thread-Topic: follow up Hadoop mavenization work
Thread-Index: AcxONMVo8oaAVWBIRASZ6XoiD3bNZQAGGGKw
Message-ID: 
 <F4FCE59AE46B2243922F224426BC869B01F3124B73@RHV-MEXMS-002.corp.ebay.com>
References: 
 <CAJs-t7N7W6Kyo4gwx7ymf8rjDSRjCpJJyrO46BE7kEX+=JY4cg@mail.gmail.com>
 <CA586F96.4726B%scott@richrelevance.com>
In-Reply-To: <CA586F96.4726B%scott@richrelevance.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Sounds good. Will give this a try on trunk after patch merges in.

Thanks,

Joep

-----Original Message-----
From: Scott Carey [mailto:scott@richrelevance.com]=20
Sent: Friday, July 29, 2011 2:18 PM
To: general@hadoop.apache.org
Subject: Re: follow up Hadoop mavenization work


On 7/29/11 8:00 AM, "Alejandro Abdelnur" <tucu@cloudera.com> wrote:

>Hi Joep,
>
>Regarding your first paragraph question, this is a byproduct of using=20
>maven.

It should be possible to clean your local repo, then type 'mvn compile' on =
the top level pom (aggregator of common, mapreduce, hdfs) and have that suc=
ceed without ever publishing any SNAPSHOTs from projects contained in the a=
ggregator.

Otherwise the project is misconfigured, or there is a buggy plugin in use.

Likewise for all other lifecycle goals prior to 'install'.  These should su=
cceed without any prior published SNAPSHOTS from modules contained in the b=
uild.

However, if you build only a submodule from the submodule pom,  (example, m=
ove down into hdfs), it will require a published snapshot from dependencies=
 such as common.