Looks like there are some wrinkles in the hadoop-0.20.2.pom that need to be ironed out:
1) the artifactId and groupId of jetty were switched in the hadoop pom (should be groupId: org.mortbay.jetty, artifactId: jetty, not the other way around) 2) the version of commons-cli 2.0 referenced in the hadoop pom couldn't be found anywhere by maven (replaced with: groupId org.apache.mahout.commons, version: 2.0-mahout for now) I made these changes and re-installed the dependency into my local repo using mvn install:install-file as described below. Also a number of the dependencies declared in the hadoop pom use properties to pick up their versions. As a result, I had to define these at the command-line (in the near term, these could be included in maven/pom.xml instead) mvn clean install -Dcommons-logging.version=1.1 -Dlog4j.version=1.2.15 -Dslf4j-api.version=1.5.8 -Dslf4j-log4j12.version=1.5.8 -Dservlet-api.version=2.5 -DskipTests=true -Djetty.version=6.1.19 -Dapacheant.version=1.7.1 SO, once all that was done I was able to complete a mahout build against the hadoop 0.20.2 release. Trying a second time running the unit tests now. Drew On Thu, Mar 4, 2010 at 11:31 PM, Robin Anil <robin.a...@gmail.com> wrote: > Coolness! Finally :) > > > On Fri, Mar 5, 2010 at 9:43 AM, Drew Farris <drew.far...@gmail.com> wrote: > >> FWIW, it looks like the 0.20.2 release ships with a pom. For those >> interested in installing it locally as a depedency until it is up on a >> repo, it is as easy as: >> >> mvn install:install-file -Dfile=hadoop-0.20.2-core.jar >> -DgroupId=org.apache.hadoop -DartifactId=hadoop-core -Dversion=0.20.2 >> -DpomFile=ivy/hadoop-core.pom >> >> From the untarred release directory. Mahout can be updated to use it >> by changing the hadoop version in maven/pom.xml from 0.20.2-SNAPSHOT >> to 0.20.2 -- doing a build against it as I type to see if there are >> any issues. >> >> Drew >> >> On Thu, Mar 4, 2010 at 10:11 AM, Drew Farris <drew.far...@gmail.com> >> wrote: >> > Yes, I asked on general and followed up on common-dev just this morning. >> > >> > Hopefully we wont have to deploy it ourselves, but I will be happy to >> take >> > care of it if we need to. >> > >> > If the release doesn't ship with a pom, we should update the pom for the >> > snapshot instead of having the deploy mojo generate one for us because >> the >> > latter won't handle hadoop D'Epagnier properly. >> > >> > How long should we wait to see if the hadoop team will handle the deploy? >> > >> > On Mar 4, 2010 8:57 AM, "Robin Anil" <robin.a...@gmail.com> wrote: >> > >> > I am +1 on us going forward if there is no response. >> > >> > Robin >> > >> > On Thu, Mar 4, 2010 at 7:26 PM, Robin Anil <robin.a...@gmail.com> wrote: >> > >> >> Drew asked the same Q o... >> >
