Well, of course. We made ours work by carefully tuning our use of the assembly plugin to make sure that all the mahout jobs ended up in the 'unpacked' part of the circus, and Math and other dependencies ended up jarred up in lib.
On Sun, May 8, 2011 at 7:01 PM, Sean Owen <[email protected]> wrote: > Yea that's how I use it too ... but in my own larger structures I do > repackage the .class files into the top level of the .jar to get it to > work. I ran into the same thing as Jake. If it's not just me, there > ought to be a solution. > > What if I removed the <unpack> stanzas in job.xml -- what would go > wrong? Meaning, as it fixes the issue, if it doesn't do harm, let's > make that change. > > On Sun, May 8, 2011 at 11:58 PM, Benson Margulies <[email protected]> > wrote: >> I'm not clear on how people manage to make the stock build fail. My >> experience has been in trying to build Mahout jobs into larger >> structures. >
