I have been able to replicate this today but I was still unable to find an
workaround.

Could it be possible that the Hadoop 0.23.1 pom file is not compatible with
maven 2.2.1? Everything seems to be working fine with maven 3? Do we want
to
enforce maven 3?

-- Andrei Savu

On Tue, Mar 20, 2012 at 3:14 AM, Alex Heneveld <
[email protected]> wrote:

> Thanks for the feedback.
>
> This is working now, but took a couple of attempts.  I suspect either repo
> availability problem or a maven-on-ubuntu version problem (maven2 versions)
> wrt hadoop-client's pom.
>
> On a side note I wonder whether yarn could use default ${hadoop.version}
> -- currently it is hard-coded against 0.23.1 for hadoop-client scope test;
> whereas /pom.xml declares 0.20.205.0 for most things hadoop.
>
> BTW here are the facts of the build problem, in case it comes up
> again/elsewhere:
>
> - wiping .m2/repo/org/apache didn't fix it on the problematic machines
> (even whilst wiping that dir _did_ cause a successful build on other
> machines)
> - there were two problematic machines; both Ubuntu, one Jenkins (maven
> 3.0.3 allegedly) and one a dev box (out-of-the-box apt-get maven2, not sure
> which version)
> - doing a manual install of maven 3.0.3 and clean install in yarn dir
> seems to fix it
>
> --A
>
>
> On 19/03/2012 15:42, Ashish wrote:
>
>> Build is working fine for me as well.
>>
>> On Mon, Mar 19, 2012 at 8:40 PM, Andrei Savu<[email protected]>
>>  wrote:
>>
>>> I'm unable to reproduce the build failure on trunk even after remove
>>> ~/.m2/repository/org/apache
>>>
>>> Could this be a partial download error that will go away on retry?
>>>
>>> On Mon, Mar 19, 2012 at 4:40 PM, Andrei Savu<[email protected]>
>>>  wrote:
>>>
>>>  Builds fine for me but it's possible that my maven cache already
>>>> contains
>>>> that fail. I will remove everything under org.apache and try again.
>>>>
>>>>
>>>> On Mon, Mar 19, 2012 at 4:34 PM, Alex Heneveld<
>>>> alex.heneveld@cloudsoftcorp.**com <[email protected]>>
>>>>  wrote:
>>>>
>>>>  Hi folks-
>>>>>
>>>>> Is anyone else having problems building Whirr head?
>>>>>
>>>>> Looks like Yarn problem pulling in Apache.
>>>>>
>>>>> I get:
>>>>>
>>>>> [INFO] --- maven-compiler-plugin:2.3.2:****testCompile
>>>>> (default-testCompile) @ whirr-yarn ---
>>>>> [INFO] Compiling 3 source files to /home/jenkins/.jenkins/jobs/****
>>>>> Apache
>>>>> Whirr/workspace/services/yarn/****target/test-classes
>>>>> [INFO] ------------------------------****----------------------------*
>>>>> *--**-
>>>>> [ERROR] COMPILATION ERROR :
>>>>> [INFO] ------------------------------****----------------------------*
>>>>> *--**-
>>>>> [ERROR] /home/jenkins/.jenkins/jobs/****Apache
>>>>> Whirr/workspace/services/yarn/****src/test/java/org/apache/**
>>>>> whirr/service/yarn/****integration/****AbstractHadoopServiceTest.****
>>>>> java:[32,29]
>>>>> package org.apache.hadoop.conf does not exist
>>>>>
>>>>>
>>>>> Almost certainly due to:
>>>>>
>>>>> Downloaded:http://repo1.maven.****org/maven2/org/apache/**hadoop/**
>>>>> hadoop-main/0.23.1/hadoop-****main-0.23.1.pom<http://repo1.**
>>>>> maven.org/maven2/org/apache/**hadoop/hadoop-main/0.23.1/**
>>>>> hadoop-main-0.23.1.pom<http://repo1.maven.org/maven2/org/apache/hadoop/hadoop-main/0.23.1/hadoop-main-0.23.1.pom>>
>>>>>  (13 KB at 42.6 KB/sec)
>>>>> [WARNING] The POM for org.apache.hadoop:hadoop-****client:jar:0.23.1
>>>>> is
>>>>> invalid, transitive dependencies (if any) will not be available, enable
>>>>> debug logging for more details
>>>>>
>>>>>
>>>>> --A
>>>>>
>>>>>
>>>>>
>>
>>
>

Reply via email to