[jira] Created: (MAPREDUCE-2182) vaidya does not compile

2010-11-10 Thread Eli Collins (JIRA)
vaidya does not compile --- Key: MAPREDUCE-2182 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2182 Project: Hadoop Map/Reduce Issue Type: Bug Components: contrib/vaidya Affects Versions: 0.22.0

Build failed in Hudson: Hadoop-Mapreduce-trunk-Commit #537

2010-11-10 Thread Apache Hudson Server
See Changes: [amareshwari] Fixes Context.setStatus() and progress() apis. Contributed by Amareshwari Sriramadasu -- [...truncated 3434 lines...] [exec] make[1]: Leaving

Re: Trunk build failing with ivy errors

2010-11-10 Thread Tom White
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 wrote: > We did a bit more sleuthing and figured out that the pom for the most rec

Re: Trunk build failing with ivy errors

2010-11-10 Thread Todd Lipcon
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://repos

Re: Trunk build failing with ivy errors

2010-11-10 Thread Owen O'Malley
On Wed, Nov 10, 2010 at 3:48 PM, Todd Lipcon 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

Re: Trunk build failing with ivy errors

2010-11-10 Thread Todd Lipcon
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 wrote: > There was a thread last week where Steve L said the jar is purposefully > missing due to some license issues and it's no

Re: Trunk build failing with ivy errors

2010-11-10 Thread Todd Lipcon
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 th

Re: Trunk build failing with ivy errors

2010-11-10 Thread Giridharan Kesavan
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

Trunk build failing with ivy errors

2010-11-10 Thread Todd Lipcon
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: trie