Could I be stupid for a moment? Our fellow Apache project, Hadoop, makes releases but doesn't bother to stick them into the Apache repo where they will replicate to central?
Are we proposing to just do their work for them, or to publish them under a Mahout-specific Maven triple? If the later, I would ask our esteemed PMC chair to make a personal approach to their PMC chair to find a way to get this done right. On Fri, Mar 5, 2010 at 7:11 AM, Drew Farris <drew.far...@gmail.com> wrote: > OK, Sean. I still need to take a final pass over the pom: > > I'll replace the placeholder version variables with real versions and > switch the group to be org.apache.mahout.hadoop (as before) instead of > org.apache.hadoop. Once the pom's in good shape, I'll switch the > dependency in mahout, do a full release build to test, do a > gpg-sign-and-deploy of the new hadoop artifact to the apache repo and > then finally commit the mahout pom referencing the new version. > > If this sounds good to everyone I'll take a crack at it this evening. > That should be enough time for anyone to give objections or alternate > suggestions, right? > > Drew > > On Fri, Mar 5, 2010 at 5:17 AM, Sean Owen <sro...@gmail.com> wrote: > > If you have the mojo ready and working, commit? Sounds OK to me. > > > > On Fri, Mar 5, 2010 at 5:14 AM, Drew Farris <drew.far...@gmail.com> > wrote: > >> Ok, the unit tests completed successfully with this setup. I suspect > >> this means we probably want to deploy our own dependency for hadoop > >> 0.20.2 with the proper versions specified in the pom itself. > > >
