hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom White <...@cloudera.com>
Subject Re: Trunk build failing with ivy errors
Date Thu, 11 Nov 2010 00:28:25 GMT
I just manually pushed new snapshots and HDFS and MapReduce trunk now
resolve artifacts and compile correctly. So it looks like Hudson is
breaking the poms somehow.

Tom

On Wed, Nov 10, 2010 at 4:16 PM, Todd Lipcon <todd@cloudera.com> wrote:
> We did a bit more sleuthing and figured out that the pom for the most recent
> hadoop-common build is screwed up. Compare:
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/hadoop-common/0.22.0-SNAPSHOT/hadoop-common-0.22.0-20101108.213242-128.pom
>
> versus:
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/hadoop-common/0.22.0-SNAPSHOT/hadoop-common-0.22.0-20101110.214513-129.pom
>
> The more recent (-129) pom has none of the substitutions completed, etc. It
> looks like the template was posted as the pom instead of the pom itself.
> Build -130 has the same issue.
>
> Did something change about the Common hudson build in the last 2 days that
> could have broken the pom publish process?
>
> -Todd
>
> On Wed, Nov 10, 2010 at 4:03 PM, Owen O'Malley <omalley@apache.org> wrote:
>
>> On Wed, Nov 10, 2010 at 3:48 PM, Todd Lipcon <todd@cloudera.com> wrote:
>>
>> > Tom has discovered that bumping the log4j version to 1.2.16 instead of
>> > 1.2.15 fixes the issue...
>> >
>> > should we just do that?
>>
>>
>> I think that sounds reasonable.
>>
>> -- Owen
>>
>
>
>
> --
> Todd Lipcon
> Software Engineer, Cloudera
>

Mime
View raw message