Subject: The perennial "Error: java.lang.ClassNotFoundException: org.apache.mahout.math.Vector" problem


I see no reason to stop using the 'lib/' convention in our jobs.

There are apparently plenty of people out there who don't know
anything about the distributed cache. If we require it's use to run
simple jobs, we're going to be up to our ears in support email.

I favor the following strategy:

1) Make sure that the split between 'libs/' and unpacked classes in
our job jars is *correct* so that all the operations of the mahout
command work out of the box.

2) post 0.5, act on the proposed refactoring so that none of our code
is calling setJarFromClass in a way that forces users to do complex
re-shading for themselves. That's the 'bean' proposal, in which each
of our jobs is a bean, and a user who wants to combine ours and theirs
can make their own call to setJar/setJarFromClass appropriately.