You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by Alex Heneveld <al...@cloudsoftcorp.com> on 2012/03/20 02:14:30 UTC
Re: maven version / resolution problem (was "problems building yarn?")
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<sa...@gmail.com> 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<sa...@gmail.com> 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> 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> (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
>>>>
>>>>
>
>
Re: maven version / resolution problem (was "problems building yarn?")
Posted by Tom White <to...@cloudera.com>.
On Tue, Mar 20, 2012 at 4:14 PM, Andrei Savu <sa...@gmail.com> wrote:
> 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?
Hadoop 0.23 requires Maven 3, so that could be it. I think we should
enforce Maven 3 for Whirr.
Tom
>
> -- Andrei Savu
>
> On Tue, Mar 20, 2012 at 3:14 AM, Alex Heneveld <
> alex.heneveld@cloudsoftcorp.com> 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<sa...@gmail.com>
>>> 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<sa...@gmail.com>
>>>> 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 <al...@cloudsoftcorp.com>>
>>>>> 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
>>>>>>
>>>>>>
>>>>>>
>>>
>>>
>>
Re: maven version / resolution problem (was "problems building yarn?")
Posted by Andrei Savu <sa...@gmail.com>.
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 <
alex.heneveld@cloudsoftcorp.com> 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<sa...@gmail.com>
>> 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<sa...@gmail.com>
>>> 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 <al...@cloudsoftcorp.com>>
>>>> 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
>>>>>
>>>>>
>>>>>
>>
>>
>
Re: maven version / resolution problem (was "problems building yarn?")
Posted by Frank Scholten <fr...@frankscholten.nl>.
It works with Maven 3 and when I remove the 0.20.2 Hadoop version.
On Wed, Mar 21, 2012 at 12:59 PM, Andrei Savu <sa...@gmail.com> wrote:
> Frank,
>
> Does it work for you with Maven 3? I am also using IntelliJ for development
> and I had no issues.
>
> On Tue, Mar 20, 2012 at 6:39 PM, Frank Scholten <fr...@frankscholten.nl>wrote:
>
>> I am having problems building the project in IntelliJ.
>>
>> AbstractHadoopServiceTest in Yarn won't compile
>>
>> I think it's because of the 4 Hadoop versions listed under External
>> Libraries
>>
>> 0.20.2
>> 0.23.0-cdh4b1
>> 0.20.2-cdh3u2
>> 0.20.205.0
>>
>> However running a mvn clean install in the Yarn module itself does work.
>>
>> Frank
>>
>> On Tue, Mar 20, 2012 at 2:14 AM, Alex Heneveld
>> <al...@cloudsoftcorp.com> 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<sa...@gmail.com>
>> >> 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<sa...@gmail.com>
>> >>> 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> 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
>> >
>> >>>>> (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
>> >>>>>
>> >>>>>
>> >>
>> >>
>> >
>> >
>>
Re: maven version / resolution problem (was "problems building yarn?")
Posted by Tom White <to...@cloudera.com>.
On Wed, Mar 21, 2012 at 8:29 AM, Andrei Savu <sa...@gmail.com> wrote:
> I this case do you think it's appropriate to re-open #374?
> https://issues.apache.org/jira/browse/WHIRR-374
Yes.
>
> If we make this decision we can also enable findbugs:
> https://issues.apache.org/jira/browse/WHIRR-321
That would be great - I keep thinking I'd like to run findbugs then
remembering we can't...
Tom
>
> On Wed, Mar 21, 2012 at 5:26 PM, Tom White <to...@cloudera.com> wrote:
>
>> On Wed, Mar 21, 2012 at 6:16 AM, Alex Heneveld
>> <al...@cloudsoftcorp.com> wrote:
>> > Same experience here. However installing maven3 isn't universally easy.
>> Is
>> > it worth seeing whether hadoop upstream needs maven3? Maybe it was
>> > accidental...
>>
>> I don't think it was accidental, it was done since supporting both
>> Maven 2 and 3 has some overhead in development and testing,
>> particularly in complex builds (like Hadoop's). (I don't know of
>> anyone complaining about having to install Maven 3 for Hadoop
>> development.) Installing Maven 3 is a manual process in most cases,
>> but it's not too onerous, and is probably less of a burden than
>> debugging differences between Maven 2 and 3.
>>
>> Cheers,
>> Tom
>>
>> >
>> > Best,
>> > Alex
>> > On 21 Mar 2012 12:43, "Rodrigo Duarte" <ro...@gmail.com> wrote:
>> >
>> >> I was having this same issue, but after upgrade to Maven 3 it
>> disappeared.
>> >>
>> >> On Wed, Mar 21, 2012 at 8:59 AM, Andrei Savu <sa...@gmail.com>
>> >> wrote:
>> >>
>> >> > Frank,
>> >> >
>> >> > Does it work for you with Maven 3? I am also using IntelliJ for
>> >> development
>> >> > and I had no issues.
>> >> >
>> >> > On Tue, Mar 20, 2012 at 6:39 PM, Frank Scholten <
>> frank@frankscholten.nl
>> >> > >wrote:
>> >> >
>> >> > > I am having problems building the project in IntelliJ.
>> >> > >
>> >> > > AbstractHadoopServiceTest in Yarn won't compile
>> >> > >
>> >> > > I think it's because of the 4 Hadoop versions listed under External
>> >> > > Libraries
>> >> > >
>> >> > > 0.20.2
>> >> > > 0.23.0-cdh4b1
>> >> > > 0.20.2-cdh3u2
>> >> > > 0.20.205.0
>> >> > >
>> >> > > However running a mvn clean install in the Yarn module itself does
>> >> work.
>> >> > >
>> >> > > Frank
>> >> > >
>> >> > > On Tue, Mar 20, 2012 at 2:14 AM, Alex Heneveld
>> >> > > <al...@cloudsoftcorp.com> 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<
>> savu.andrei@gmail.com>
>> >> > > >> 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<
>> savu.andrei@gmail.com
>> >> >
>> >> > > >>> 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> 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
>> >> > > >
>> >> > > >>>>> (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
>> >> > > >>>>>
>> >> > > >>>>>
>> >> > > >>
>> >> > > >>
>> >> > > >
>> >> > > >
>> >> > >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Rodrigo Duarte Sousa
>> >> MSc candidate in Computer Science
>> >> Distributed Systems Laboratory
>> >> Federal University of Campina Grande
>> >> Campina Grande, PB - Brazil
>> >> http://lsd.ufcg.edu.br/~rodrigod <http://lsd.ufcg.edu.br/%7Erodrigods>s
>> >>
>>
Re: maven version / resolution problem (was "problems building yarn?")
Posted by Alex Heneveld <al...@cloudsoftcorp.com>.
Thanks Tom. +1 maven3 then!
Best,
Alex
On 21 Mar 2012 15:30, "Andrei Savu" <sa...@gmail.com> wrote:
> I this case do you think it's appropriate to re-open #374?
> https://issues.apache.org/jira/browse/WHIRR-374
>
> If we make this decision we can also enable findbugs:
> https://issues.apache.org/jira/browse/WHIRR-321
>
> On Wed, Mar 21, 2012 at 5:26 PM, Tom White <to...@cloudera.com> wrote:
>
> > On Wed, Mar 21, 2012 at 6:16 AM, Alex Heneveld
> > <al...@cloudsoftcorp.com> wrote:
> > > Same experience here. However installing maven3 isn't universally easy.
> > Is
> > > it worth seeing whether hadoop upstream needs maven3? Maybe it was
> > > accidental...
> >
> > I don't think it was accidental, it was done since supporting both
> > Maven 2 and 3 has some overhead in development and testing,
> > particularly in complex builds (like Hadoop's). (I don't know of
> > anyone complaining about having to install Maven 3 for Hadoop
> > development.) Installing Maven 3 is a manual process in most cases,
> > but it's not too onerous, and is probably less of a burden than
> > debugging differences between Maven 2 and 3.
> >
> > Cheers,
> > Tom
> >
> > >
> > > Best,
> > > Alex
> > > On 21 Mar 2012 12:43, "Rodrigo Duarte" <ro...@gmail.com>
> wrote:
> > >
> > >> I was having this same issue, but after upgrade to Maven 3 it
> > disappeared.
> > >>
> > >> On Wed, Mar 21, 2012 at 8:59 AM, Andrei Savu <sa...@gmail.com>
> > >> wrote:
> > >>
> > >> > Frank,
> > >> >
> > >> > Does it work for you with Maven 3? I am also using IntelliJ for
> > >> development
> > >> > and I had no issues.
> > >> >
> > >> > On Tue, Mar 20, 2012 at 6:39 PM, Frank Scholten <
> > frank@frankscholten.nl
> > >> > >wrote:
> > >> >
> > >> > > I am having problems building the project in IntelliJ.
> > >> > >
> > >> > > AbstractHadoopServiceTest in Yarn won't compile
> > >> > >
> > >> > > I think it's because of the 4 Hadoop versions listed under
> External
> > >> > > Libraries
> > >> > >
> > >> > > 0.20.2
> > >> > > 0.23.0-cdh4b1
> > >> > > 0.20.2-cdh3u2
> > >> > > 0.20.205.0
> > >> > >
> > >> > > However running a mvn clean install in the Yarn module itself does
> > >> work.
> > >> > >
> > >> > > Frank
> > >> > >
> > >> > > On Tue, Mar 20, 2012 at 2:14 AM, Alex Heneveld
> > >> > > <al...@cloudsoftcorp.com> 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<
> > savu.andrei@gmail.com>
> > >> > > >> 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<
> > savu.andrei@gmail.com
> > >> >
> > >> > > >>> 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> 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
> > >> > > >
> > >> > > >>>>> (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
> > >> > > >>>>>
> > >> > > >>>>>
> > >> > > >>
> > >> > > >>
> > >> > > >
> > >> > > >
> > >> > >
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> Rodrigo Duarte Sousa
> > >> MSc candidate in Computer Science
> > >> Distributed Systems Laboratory
> > >> Federal University of Campina Grande
> > >> Campina Grande, PB - Brazil
> > >> http://lsd.ufcg.edu.br/~rodrigod <http://lsd.ufcg.edu.br/%7Erodrigods
> >s
> > >>
> >
>
Re: maven version / resolution problem (was "problems building yarn?")
Posted by Andrei Savu <sa...@gmail.com>.
I this case do you think it's appropriate to re-open #374?
https://issues.apache.org/jira/browse/WHIRR-374
If we make this decision we can also enable findbugs:
https://issues.apache.org/jira/browse/WHIRR-321
On Wed, Mar 21, 2012 at 5:26 PM, Tom White <to...@cloudera.com> wrote:
> On Wed, Mar 21, 2012 at 6:16 AM, Alex Heneveld
> <al...@cloudsoftcorp.com> wrote:
> > Same experience here. However installing maven3 isn't universally easy.
> Is
> > it worth seeing whether hadoop upstream needs maven3? Maybe it was
> > accidental...
>
> I don't think it was accidental, it was done since supporting both
> Maven 2 and 3 has some overhead in development and testing,
> particularly in complex builds (like Hadoop's). (I don't know of
> anyone complaining about having to install Maven 3 for Hadoop
> development.) Installing Maven 3 is a manual process in most cases,
> but it's not too onerous, and is probably less of a burden than
> debugging differences between Maven 2 and 3.
>
> Cheers,
> Tom
>
> >
> > Best,
> > Alex
> > On 21 Mar 2012 12:43, "Rodrigo Duarte" <ro...@gmail.com> wrote:
> >
> >> I was having this same issue, but after upgrade to Maven 3 it
> disappeared.
> >>
> >> On Wed, Mar 21, 2012 at 8:59 AM, Andrei Savu <sa...@gmail.com>
> >> wrote:
> >>
> >> > Frank,
> >> >
> >> > Does it work for you with Maven 3? I am also using IntelliJ for
> >> development
> >> > and I had no issues.
> >> >
> >> > On Tue, Mar 20, 2012 at 6:39 PM, Frank Scholten <
> frank@frankscholten.nl
> >> > >wrote:
> >> >
> >> > > I am having problems building the project in IntelliJ.
> >> > >
> >> > > AbstractHadoopServiceTest in Yarn won't compile
> >> > >
> >> > > I think it's because of the 4 Hadoop versions listed under External
> >> > > Libraries
> >> > >
> >> > > 0.20.2
> >> > > 0.23.0-cdh4b1
> >> > > 0.20.2-cdh3u2
> >> > > 0.20.205.0
> >> > >
> >> > > However running a mvn clean install in the Yarn module itself does
> >> work.
> >> > >
> >> > > Frank
> >> > >
> >> > > On Tue, Mar 20, 2012 at 2:14 AM, Alex Heneveld
> >> > > <al...@cloudsoftcorp.com> 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<
> savu.andrei@gmail.com>
> >> > > >> 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<
> savu.andrei@gmail.com
> >> >
> >> > > >>> 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> 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
> >> > > >
> >> > > >>>>> (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
> >> > > >>>>>
> >> > > >>>>>
> >> > > >>
> >> > > >>
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> Rodrigo Duarte Sousa
> >> MSc candidate in Computer Science
> >> Distributed Systems Laboratory
> >> Federal University of Campina Grande
> >> Campina Grande, PB - Brazil
> >> http://lsd.ufcg.edu.br/~rodrigod <http://lsd.ufcg.edu.br/%7Erodrigods>s
> >>
>
Re: maven version / resolution problem (was "problems building yarn?")
Posted by Andrei Savu <sa...@gmail.com>.
On Wed, Mar 21, 2012 at 5:40 PM, Adrian Cole <ad...@jclouds.org> wrote:
> I suppose since this is the context developers (as opposed to users) we are
> discussing, my thought is extracting the maven zip and exporting variables
> shouldn't weed out too many.
>
+1
Re: maven version / resolution problem (was "problems building yarn?")
Posted by Adrian Cole <ad...@jclouds.org>.
I suppose since this is the context developers (as opposed to users) we are
discussing, my thought is extracting the maven zip and exporting variables
shouldn't weed out too many.
Also, maven 3 is far from hot off the press. Any complaints we may get can
be redirected to package repo owners.
On Mar 21, 2012 8:27 AM, "Tom White" <to...@cloudera.com> wrote:
> On Wed, Mar 21, 2012 at 6:16 AM, Alex Heneveld
> <al...@cloudsoftcorp.com> wrote:
> > Same experience here. However installing maven3 isn't universally easy.
> Is
> > it worth seeing whether hadoop upstream needs maven3? Maybe it was
> > accidental...
>
> I don't think it was accidental, it was done since supporting both
> Maven 2 and 3 has some overhead in development and testing,
> particularly in complex builds (like Hadoop's). (I don't know of
> anyone complaining about having to install Maven 3 for Hadoop
> development.) Installing Maven 3 is a manual process in most cases,
> but it's not too onerous, and is probably less of a burden than
> debugging differences between Maven 2 and 3.
>
> Cheers,
> Tom
>
> >
> > Best,
> > Alex
> > On 21 Mar 2012 12:43, "Rodrigo Duarte" <ro...@gmail.com> wrote:
> >
> >> I was having this same issue, but after upgrade to Maven 3 it
> disappeared.
> >>
> >> On Wed, Mar 21, 2012 at 8:59 AM, Andrei Savu <sa...@gmail.com>
> >> wrote:
> >>
> >> > Frank,
> >> >
> >> > Does it work for you with Maven 3? I am also using IntelliJ for
> >> development
> >> > and I had no issues.
> >> >
> >> > On Tue, Mar 20, 2012 at 6:39 PM, Frank Scholten <
> frank@frankscholten.nl
> >> > >wrote:
> >> >
> >> > > I am having problems building the project in IntelliJ.
> >> > >
> >> > > AbstractHadoopServiceTest in Yarn won't compile
> >> > >
> >> > > I think it's because of the 4 Hadoop versions listed under External
> >> > > Libraries
> >> > >
> >> > > 0.20.2
> >> > > 0.23.0-cdh4b1
> >> > > 0.20.2-cdh3u2
> >> > > 0.20.205.0
> >> > >
> >> > > However running a mvn clean install in the Yarn module itself does
> >> work.
> >> > >
> >> > > Frank
> >> > >
> >> > > On Tue, Mar 20, 2012 at 2:14 AM, Alex Heneveld
> >> > > <al...@cloudsoftcorp.com> 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<
> savu.andrei@gmail.com>
> >> > > >> 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<
> savu.andrei@gmail.com
> >> >
> >> > > >>> 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> 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
> >> > > >
> >> > > >>>>> (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
> >> > > >>>>>
> >> > > >>>>>
> >> > > >>
> >> > > >>
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> Rodrigo Duarte Sousa
> >> MSc candidate in Computer Science
> >> Distributed Systems Laboratory
> >> Federal University of Campina Grande
> >> Campina Grande, PB - Brazil
> >> http://lsd.ufcg.edu.br/~rodrigod <http://lsd.ufcg.edu.br/%7Erodrigods>s
> >>
>
Re: maven version / resolution problem (was "problems building yarn?")
Posted by Tom White <to...@cloudera.com>.
On Wed, Mar 21, 2012 at 6:16 AM, Alex Heneveld
<al...@cloudsoftcorp.com> wrote:
> Same experience here. However installing maven3 isn't universally easy. Is
> it worth seeing whether hadoop upstream needs maven3? Maybe it was
> accidental...
I don't think it was accidental, it was done since supporting both
Maven 2 and 3 has some overhead in development and testing,
particularly in complex builds (like Hadoop's). (I don't know of
anyone complaining about having to install Maven 3 for Hadoop
development.) Installing Maven 3 is a manual process in most cases,
but it's not too onerous, and is probably less of a burden than
debugging differences between Maven 2 and 3.
Cheers,
Tom
>
> Best,
> Alex
> On 21 Mar 2012 12:43, "Rodrigo Duarte" <ro...@gmail.com> wrote:
>
>> I was having this same issue, but after upgrade to Maven 3 it disappeared.
>>
>> On Wed, Mar 21, 2012 at 8:59 AM, Andrei Savu <sa...@gmail.com>
>> wrote:
>>
>> > Frank,
>> >
>> > Does it work for you with Maven 3? I am also using IntelliJ for
>> development
>> > and I had no issues.
>> >
>> > On Tue, Mar 20, 2012 at 6:39 PM, Frank Scholten <frank@frankscholten.nl
>> > >wrote:
>> >
>> > > I am having problems building the project in IntelliJ.
>> > >
>> > > AbstractHadoopServiceTest in Yarn won't compile
>> > >
>> > > I think it's because of the 4 Hadoop versions listed under External
>> > > Libraries
>> > >
>> > > 0.20.2
>> > > 0.23.0-cdh4b1
>> > > 0.20.2-cdh3u2
>> > > 0.20.205.0
>> > >
>> > > However running a mvn clean install in the Yarn module itself does
>> work.
>> > >
>> > > Frank
>> > >
>> > > On Tue, Mar 20, 2012 at 2:14 AM, Alex Heneveld
>> > > <al...@cloudsoftcorp.com> 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<sa...@gmail.com>
>> > > >> 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<savu.andrei@gmail.com
>> >
>> > > >>> 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> 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
>> > > >
>> > > >>>>> (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
>> > > >>>>>
>> > > >>>>>
>> > > >>
>> > > >>
>> > > >
>> > > >
>> > >
>> >
>>
>>
>>
>> --
>> Rodrigo Duarte Sousa
>> MSc candidate in Computer Science
>> Distributed Systems Laboratory
>> Federal University of Campina Grande
>> Campina Grande, PB - Brazil
>> http://lsd.ufcg.edu.br/~rodrigod <http://lsd.ufcg.edu.br/%7Erodrigods>s
>>
Re: maven version / resolution problem (was "problems building yarn?")
Posted by Alex Heneveld <al...@cloudsoftcorp.com>.
Same experience here. However installing maven3 isn't universally easy. Is
it worth seeing whether hadoop upstream needs maven3? Maybe it was
accidental...
Best,
Alex
On 21 Mar 2012 12:43, "Rodrigo Duarte" <ro...@gmail.com> wrote:
> I was having this same issue, but after upgrade to Maven 3 it disappeared.
>
> On Wed, Mar 21, 2012 at 8:59 AM, Andrei Savu <sa...@gmail.com>
> wrote:
>
> > Frank,
> >
> > Does it work for you with Maven 3? I am also using IntelliJ for
> development
> > and I had no issues.
> >
> > On Tue, Mar 20, 2012 at 6:39 PM, Frank Scholten <frank@frankscholten.nl
> > >wrote:
> >
> > > I am having problems building the project in IntelliJ.
> > >
> > > AbstractHadoopServiceTest in Yarn won't compile
> > >
> > > I think it's because of the 4 Hadoop versions listed under External
> > > Libraries
> > >
> > > 0.20.2
> > > 0.23.0-cdh4b1
> > > 0.20.2-cdh3u2
> > > 0.20.205.0
> > >
> > > However running a mvn clean install in the Yarn module itself does
> work.
> > >
> > > Frank
> > >
> > > On Tue, Mar 20, 2012 at 2:14 AM, Alex Heneveld
> > > <al...@cloudsoftcorp.com> 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<sa...@gmail.com>
> > > >> 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<savu.andrei@gmail.com
> >
> > > >>> 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> 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
> > > >
> > > >>>>> (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
> > > >>>>>
> > > >>>>>
> > > >>
> > > >>
> > > >
> > > >
> > >
> >
>
>
>
> --
> Rodrigo Duarte Sousa
> MSc candidate in Computer Science
> Distributed Systems Laboratory
> Federal University of Campina Grande
> Campina Grande, PB - Brazil
> http://lsd.ufcg.edu.br/~rodrigod <http://lsd.ufcg.edu.br/%7Erodrigods>s
>
Re: maven version / resolution problem (was "problems building yarn?")
Posted by Rodrigo Duarte <ro...@gmail.com>.
I was having this same issue, but after upgrade to Maven 3 it disappeared.
On Wed, Mar 21, 2012 at 8:59 AM, Andrei Savu <sa...@gmail.com> wrote:
> Frank,
>
> Does it work for you with Maven 3? I am also using IntelliJ for development
> and I had no issues.
>
> On Tue, Mar 20, 2012 at 6:39 PM, Frank Scholten <frank@frankscholten.nl
> >wrote:
>
> > I am having problems building the project in IntelliJ.
> >
> > AbstractHadoopServiceTest in Yarn won't compile
> >
> > I think it's because of the 4 Hadoop versions listed under External
> > Libraries
> >
> > 0.20.2
> > 0.23.0-cdh4b1
> > 0.20.2-cdh3u2
> > 0.20.205.0
> >
> > However running a mvn clean install in the Yarn module itself does work.
> >
> > Frank
> >
> > On Tue, Mar 20, 2012 at 2:14 AM, Alex Heneveld
> > <al...@cloudsoftcorp.com> 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<sa...@gmail.com>
> > >> 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<sa...@gmail.com>
> > >>> 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> 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
> > >
> > >>>>> (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
> > >>>>>
> > >>>>>
> > >>
> > >>
> > >
> > >
> >
>
--
Rodrigo Duarte Sousa
MSc candidate in Computer Science
Distributed Systems Laboratory
Federal University of Campina Grande
Campina Grande, PB - Brazil
http://lsd.ufcg.edu.br/~rodrigod <http://lsd.ufcg.edu.br/%7Erodrigods>s
Re: maven version / resolution problem (was "problems building yarn?")
Posted by Andrei Savu <sa...@gmail.com>.
Frank,
Does it work for you with Maven 3? I am also using IntelliJ for development
and I had no issues.
On Tue, Mar 20, 2012 at 6:39 PM, Frank Scholten <fr...@frankscholten.nl>wrote:
> I am having problems building the project in IntelliJ.
>
> AbstractHadoopServiceTest in Yarn won't compile
>
> I think it's because of the 4 Hadoop versions listed under External
> Libraries
>
> 0.20.2
> 0.23.0-cdh4b1
> 0.20.2-cdh3u2
> 0.20.205.0
>
> However running a mvn clean install in the Yarn module itself does work.
>
> Frank
>
> On Tue, Mar 20, 2012 at 2:14 AM, Alex Heneveld
> <al...@cloudsoftcorp.com> 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<sa...@gmail.com>
> >> 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<sa...@gmail.com>
> >>> 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> 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
> >
> >>>>> (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
> >>>>>
> >>>>>
> >>
> >>
> >
> >
>
Re: maven version / resolution problem (was "problems building yarn?")
Posted by Tom White <to...@cloudera.com>.
On Tue, Mar 20, 2012 at 9:39 AM, Frank Scholten <fr...@frankscholten.nl> wrote:
> I am having problems building the project in IntelliJ.
>
> AbstractHadoopServiceTest in Yarn won't compile
>
> I think it's because of the 4 Hadoop versions listed under External Libraries
>
> 0.20.2
> 0.23.0-cdh4b1
> 0.20.2-cdh3u2
> 0.20.205.0
Having 0.20.2 and 0.20.205.0 looks wrong. Can you remove the
definition of hadoop.version in the YARN POM and see if that helps?
Tom
>
> However running a mvn clean install in the Yarn module itself does work.
>
> Frank
>
> On Tue, Mar 20, 2012 at 2:14 AM, Alex Heneveld
> <al...@cloudsoftcorp.com> 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<sa...@gmail.com>
>>> 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<sa...@gmail.com>
>>>> 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> 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>
>>>>>> (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
>>>>>>
>>>>>>
>>>
>>>
>>
>>
Re: maven version / resolution problem (was "problems building yarn?")
Posted by Frank Scholten <fr...@frankscholten.nl>.
I am having problems building the project in IntelliJ.
AbstractHadoopServiceTest in Yarn won't compile
I think it's because of the 4 Hadoop versions listed under External Libraries
0.20.2
0.23.0-cdh4b1
0.20.2-cdh3u2
0.20.205.0
However running a mvn clean install in the Yarn module itself does work.
Frank
On Tue, Mar 20, 2012 at 2:14 AM, Alex Heneveld
<al...@cloudsoftcorp.com> 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<sa...@gmail.com>
>> 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<sa...@gmail.com>
>>> 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> 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>
>>>>> (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
>>>>>
>>>>>
>>
>>
>
>