Subject: -- misplaced calls to setJarByClass

I just did some belated reading which at leads me to want to do a bit
more homework here.

The official semantics of setJar are to specify which jar file has to
be carried around from node to node to distribute the mapper and
reducer. The connection of this to the 'can't find the analyzer class'
business, I realize, is not quite clear. It is acting as if calling
setJar with a name of a jar in the lib dir of the main jar might cause
just that jar to travel around, and that would indeed cause the havoc
that started all this, but I want to prove it before I start poking