As of this afternoon I'm not able to build mapreduce trunk. It fails to pull
some JMS jars - not sure how these are getting pulled in in the first
place...

[ivy:resolve] :::: WARNINGS
[ivy:resolve]           [FAILED     ] javax.jms#jms;1.1!jms.jar:  (0ms)
[ivy:resolve]   ==== apache-snapshot: tried
[ivy:resolve]
https://repository.apache.org/content/repositories/snapshots/javax/jms/jms/1.1/jms-1.1.jar
[ivy:resolve]   ==== maven2: tried
[ivy:resolve]
http://repo1.maven.org/maven2/javax/jms/jms/1.1/jms-1.1.jar
[ivy:resolve]           [FAILED     ]
com.sun.jdmk#jmxtools;1.2.1!jmxtools.jar:  (0ms)
[ivy:resolve]   ==== apache-snapshot: tried
[ivy:resolve]
https://repository.apache.org/content/repositories/snapshots/com/sun/jdmk/jmxtools/1.2.1/jmxtools-1.2.1.jar
[ivy:resolve]   ==== maven2: tried
[ivy:resolve]
http://repo1.maven.org/maven2/com/sun/jdmk/jmxtools/1.2.1/jmxtools-1.2.1.jar
[ivy:resolve]           [FAILED     ] com.sun.jmx#jmxri;1.2.1!jmxri.jar:
 (0ms)
[ivy:resolve]   ==== apache-snapshot: tried
[ivy:resolve]
https://repository.apache.org/content/repositories/snapshots/com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.jar
[ivy:resolve]   ==== maven2: tried
[ivy:resolve]
http://repo1.maven.org/maven2/com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.jar
[ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve]           ::              FAILED DOWNLOADS            ::
[ivy:resolve]           :: ^ see resolution messages for details  ^ ::
[ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve]           :: javax.jms#jms;1.1!jms.jar
[ivy:resolve]           :: com.sun.jdmk#jmxtools;1.2.1!jmxtools.jar
[ivy:resolve]           :: com.sun.jmx#jmxri;1.2.1!jmxri.jar
[ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::

Anyone have any idea what's going on here? Did we pick up a transitive
dependency on jmx somehow? I'll keep poking around and see if I can see
what's happening.

-Todd
--
Todd Lipcon
Software Engineer, Cloudera

This the mvn repo link where ivy downloads the jms jar.

http://repo1.maven.org/maven2/javax/jms/jms/1.1/

Looking at the above link, the jar file alone is missing..

this happened the second time since last week. I ve seen the same issue last week and after that It just vanished itself.

I think we should include the jboss maven repo part of the ivysettings which has the jms.jar

http://repository.jboss.org/maven2/javax/jms/jms

Thanks,
Giri

On Nov 10, 2010, at 3:21 PM, Todd Lipcon wrote:

> As of this afternoon I'm not able to build mapreduce trunk. It fails to pull
> some JMS jars - not sure how these are getting pulled in in the first
> place...
>
> [ivy:resolve] :::: WARNINGS
> [ivy:resolve]           [FAILED     ] javax.jms#jms;1.1!jms.jar:  (0ms)
> [ivy:resolve]   ==== apache-snapshot: tried
> [ivy:resolve]
> https://repository.apache.org/content/repositories/snapshots/javax/jms/jms/1.1/jms-1.1.jar
> [ivy:resolve]   ==== maven2: tried
> [ivy:resolve]
> http://repo1.maven.org/maven2/javax/jms/jms/1.1/jms-1.1.jar
> [ivy:resolve]           [FAILED     ]
> com.sun.jdmk#jmxtools;1.2.1!jmxtools.jar:  (0ms)
> [ivy:resolve]   ==== apache-snapshot: tried
> [ivy:resolve]
> https://repository.apache.org/content/repositories/snapshots/com/sun/jdmk/jmxtools/1.2.1/jmxtools-1.2.1.jar
> [ivy:resolve]   ==== maven2: tried
> [ivy:resolve]
> http://repo1.maven.org/maven2/com/sun/jdmk/jmxtools/1.2.1/jmxtools-1.2.1.jar
> [ivy:resolve]           [FAILED     ] com.sun.jmx#jmxri;1.2.1!jmxri.jar:
> (0ms)
> [ivy:resolve]   ==== apache-snapshot: tried
> [ivy:resolve]
> https://repository.apache.org/content/repositories/snapshots/com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.jar
> [ivy:resolve]   ==== maven2: tried
> [ivy:resolve]
> http://repo1.maven.org/maven2/com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.jar
> [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:resolve]           ::              FAILED DOWNLOADS            ::
> [ivy:resolve]           :: ^ see resolution messages for details  ^ ::
> [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:resolve]           :: javax.jms#jms;1.1!jms.jar
> [ivy:resolve]           :: com.sun.jdmk#jmxtools;1.2.1!jmxtools.jar
> [ivy:resolve]           :: com.sun.jmx#jmxri;1.2.1!jmxri.jar
> [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
>
> Anyone have any idea what's going on here? Did we pick up a transitive
> dependency on jmx somehow? I'll keep poking around and see if I can see
> what's happening.
>
> -Todd
> --
> Todd Lipcon
> Software Engineer, Cloudera

There was a thread last week where Steve L said the jar is purposefully
missing due to some license issues and it's not new. If you look at the
modification date of the 1.1 dir, it's from 2007.

Any chance something changed in one of our repos that added a transitive
dependency? Maybe your patch that was committed that adds wagon-http to
hdfs?

-Todd
On Wed, Nov 10, 2010 at 3:32 PM, Giridharan Kesavan
<[EMAIL PROTECTED]>wrote:

> This the mvn repo link where ivy downloads the jms jar.
>
> http://repo1.maven.org/maven2/javax/jms/jms/1.1/
>
> Looking at the above link, the jar file alone is missing..
>
> this happened the second time since last week. I ve seen the same issue
> last week and after that It just vanished itself.
>
> I think we should include the jboss maven repo part of the ivysettings
> which has the jms.jar
>
> http://repository.jboss.org/maven2/javax/jms/jms
>
> Thanks,
> Giri
>
> On Nov 10, 2010, at 3:21 PM, Todd Lipcon wrote:
>
> > As of this afternoon I'm not able to build mapreduce trunk. It fails to
> pull
> > some JMS jars - not sure how these are getting pulled in in the first
> > place...
> >
> > [ivy:resolve] :::: WARNINGS
> > [ivy:resolve]           [FAILED     ] javax.jms#jms;1.1!jms.jar:  (0ms)
> > [ivy:resolve]   ==== apache-snapshot: tried
> > [ivy:resolve]
> >
> https://repository.apache.org/content/repositories/snapshots/javax/jms/jms/1.1/jms-1.1.jar
> > [ivy:resolve]   ==== maven2: tried
> > [ivy:resolve]
> > http://repo1.maven.org/maven2/javax/jms/jms/1.1/jms-1.1.jar
> > [ivy:resolve]           [FAILED     ]
> > com.sun.jdmk#jmxtools;1.2.1!jmxtools.jar:  (0ms)
> > [ivy:resolve]   ==== apache-snapshot: tried
> > [ivy:resolve]
> >
> https://repository.apache.org/content/repositories/snapshots/com/sun/jdmk/jmxtools/1.2.1/jmxtools-1.2.1.jar
> > [ivy:resolve]   ==== maven2: tried
> > [ivy:resolve]
> >
> http://repo1.maven.org/maven2/com/sun/jdmk/jmxtools/1.2.1/jmxtools-1.2.1.jar
> > [ivy:resolve]           [FAILED     ] com.sun.jmx#jmxri;1.2.1!jmxri.jar:
> > (0ms)
> > [ivy:resolve]   ==== apache-snapshot: tried
> > [ivy:resolve]
> >
> https://repository.apache.org/content/repositories/snapshots/com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.jar
> > [ivy:resolve]   ==== maven2: tried
> > [ivy:resolve]
> > http://repo1.maven.org/maven2/com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.jar
> > [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
> > [ivy:resolve]           ::              FAILED DOWNLOADS            ::
> > [ivy:resolve]           :: ^ see resolution messages for details  ^ ::
> > [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
> > [ivy:resolve]           :: javax.jms#jms;1.1!jms.jar
> > [ivy:resolve]           :: com.sun.jdmk#jmxtools;1.2.1!jmxtools.jar
> > [ivy:resolve]           :: com.sun.jmx#jmxri;1.2.1!jmxri.jar
> > [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
> >
> > Anyone have any idea what's going on here? Did we pick up a transitive
> > dependency on jmx somehow? I'll keep poking around and see if I can see
> > what's happening.
> >
> > -Todd
> > --
> > Todd Lipcon
> > Software Engineer, Cloudera
>
>
--
Todd Lipcon
Software Engineer, Cloudera

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?

On Wed, Nov 10, 2010 at 3:36 PM, Todd Lipcon <[EMAIL PROTECTED]> wrote:

> There was a thread last week where Steve L said the jar is purposefully
> missing due to some license issues and it's not new. If you look at the
> modification date of the 1.1 dir, it's from 2007.
>
> Any chance something changed in one of our repos that added a transitive
> dependency? Maybe your patch that was committed that adds wagon-http to
> hdfs?
>
> -Todd
>
> On Wed, Nov 10, 2010 at 3:32 PM, Giridharan Kesavan <
> [EMAIL PROTECTED]> wrote:
>
>> This the mvn repo link where ivy downloads the jms jar.
>>
>> http://repo1.maven.org/maven2/javax/jms/jms/1.1/
>>
>> Looking at the above link, the jar file alone is missing..
>>
>> this happened the second time since last week. I ve seen the same issue
>> last week and after that It just vanished itself.
>>
>> I think we should include the jboss maven repo part of the ivysettings
>> which has the jms.jar
>>
>> http://repository.jboss.org/maven2/javax/jms/jms
>>
>> Thanks,
>> Giri
>>
>> On Nov 10, 2010, at 3:21 PM, Todd Lipcon wrote:
>>
>> > As of this afternoon I'm not able to build mapreduce trunk. It fails to
>> pull
>> > some JMS jars - not sure how these are getting pulled in in the first
>> > place...
>> >
>> > [ivy:resolve] :::: WARNINGS
>> > [ivy:resolve]           [FAILED     ] javax.jms#jms;1.1!jms.jar:  (0ms)
>> > [ivy:resolve]   ==== apache-snapshot: tried
>> > [ivy:resolve]
>> >
>> https://repository.apache.org/content/repositories/snapshots/javax/jms/jms/1.1/jms-1.1.jar
>> > [ivy:resolve]   ==== maven2: tried
>> > [ivy:resolve]
>> > http://repo1.maven.org/maven2/javax/jms/jms/1.1/jms-1.1.jar
>> > [ivy:resolve]           [FAILED     ]
>> > com.sun.jdmk#jmxtools;1.2.1!jmxtools.jar:  (0ms)
>> > [ivy:resolve]   ==== apache-snapshot: tried
>> > [ivy:resolve]
>> >
>> https://repository.apache.org/content/repositories/snapshots/com/sun/jdmk/jmxtools/1.2.1/jmxtools-1.2.1.jar
>> > [ivy:resolve]   ==== maven2: tried
>> > [ivy:resolve]
>> >
>> http://repo1.maven.org/maven2/com/sun/jdmk/jmxtools/1.2.1/jmxtools-1.2.1.jar
>> > [ivy:resolve]           [FAILED     ] com.sun.jmx#jmxri;1.2.1!jmxri.jar:
>> > (0ms)
>> > [ivy:resolve]   ==== apache-snapshot: tried
>> > [ivy:resolve]
>> >
>> https://repository.apache.org/content/repositories/snapshots/com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.jar
>> > [ivy:resolve]   ==== maven2: tried
>> > [ivy:resolve]
>> > http://repo1.maven.org/maven2/com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.jar
>> > [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
>> > [ivy:resolve]           ::              FAILED DOWNLOADS            ::
>> > [ivy:resolve]           :: ^ see resolution messages for details  ^ ::
>> > [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
>> > [ivy:resolve]           :: javax.jms#jms;1.1!jms.jar
>> > [ivy:resolve]           :: com.sun.jdmk#jmxtools;1.2.1!jmxtools.jar
>> > [ivy:resolve]           :: com.sun.jmx#jmxri;1.2.1!jmxri.jar
>> > [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
>> >
>> > Anyone have any idea what's going on here? Did we pick up a transitive
>> > dependency on jmx somehow? I'll keep poking around and see if I can see
>> > what's happening.
>> >
>> > -Todd
>> > --
>> > Todd Lipcon
>> > Software Engineer, Cloudera
>>
>>
>
>
> --
> Todd Lipcon
> Software Engineer, Cloudera
>

--
Todd Lipcon
Software Engineer, Cloudera

On Wed, Nov 10, 2010 at 3:48 PM, Todd Lipcon <[EMAIL PROTECTED]> 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

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 <[EMAIL PROTECTED]> wrote:

> On Wed, Nov 10, 2010 at 3:48 PM, Todd Lipcon <[EMAIL PROTECTED]> 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

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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> wrote:
>
>> On Wed, Nov 10, 2010 at 3:48 PM, Todd Lipcon <[EMAIL PROTECTED]> 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
>