hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Giridharan Kesavan" <gkesa...@yahoo-inc.com>
Subject Re: Post-5107 cross-project commits
Date Thu, 10 Dec 2009 04:56:04 GMT
Hi Eli,

I'm able to run the same set of ant target without any problem.

Could you try this?
ant -Dresolvers=internal veryclean mvn-install


On 12/10/09 12:02 AM, "Eli Collins" <eli@cloudera.com> wrote:

Hey Owen,

Is the MR side ready yet?  It looks like the MR changes (HADOOP-5107,
MAPREDUCE-1239) went in. Building on trunk (after mvn-install'ing
common and hdfs) building mr with ant -Dresolvers=internal clean-cache
mvn-install  yields the following.

/home/eli/src/mapred1/build.xml:1148: Problem: failed to create task
or type urn:maven-artifact-ant:pom
Cause: The name is undefined.


On Fri, Oct 30, 2009 at 3:59 PM, Owen O'Malley <omalley@apache.org> wrote:
> I've committed HADOOP-5107 to Common and HDFS. MapReduce will follow soon.
> There are a couple of things that change:
> 1. The non-release version names move to the Maven-friendly 0.22.0-SNAPSHOT
> instead of 0.22.0-dev.
> 2. To change Common and push it to your local Maven repository:
>  a. make change to common
>  b. ant mvn-install
> 3. To build using your internal Maven repository and push HDFS to your local
> Maven repository:
>  a. make change to HDFS
>  b. ant -Dresolvers=internal clean-cache mvn-install
> -- Owen

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message