Hi, On Wed, Nov 11, 2009 at 8:50 PM, Grant Ingersoll <[email protected]> wrote: > On Nov 11, 2009, at 1:45 PM, Jukka Zitting wrote: >> The standard and by far the easiest way to get this dependency >> included in the Mahout build is to ask the Hadoop project do deploy it >> under the org.apache.hadoop groupId. > > They are working on it, but don't have it for our versions.
I pinged the Hadoop dev list about this, see http://markmail.org/message/643sxbyjcrjxaglt. Hopefully that'll speed things up, though for Mahout 0.2 the dependency may still need to be deployed to org.apache.mahout.hadoop. > We also have other non-Hadoop deps that aren't published, so they > need to be deployed and signed as well (Commons CLI2). I asked Commons for a CLI 2.0 release, see http://markmail.org/message/h357fauzs4arxfsg, though for now I think Mahout can simply use the already deployed org.apache.mahout.commons:commons-cli:2.0-mahout version. I also tracked down the other dependencies that we now try to sign-and-deploy: * kfs-0.3.jar -> net.sf.kosmosfs:kfs:0.3 * jets3t-0.7.1.jar -> net.java.dev.jets3t:jets3t:0.7.1 * watchmaker-framework-0.6.2.jar -> not available * watchmaker-swing-0.6.2.jar -> not available * uncommons-maths-1.2.jar -> not availabe It should be possible to deploy the missing artifacts like this: mvn gpg:sign-and-deploy-file \ -Durl=https://repository.apache.org/service/local/staging/deploy/maven2 \ -DrepositoryId=apache.releases.https \ -DgroupId=org.apache.mahout.xxx -DartifactId=xxx \ -Dversion=xxx -Dpackaging=jar -Dfile=core/lib/xxx.jar BR, Jukka Zitting
