I have run into a similar problem. Putting jars inside jars only works if
the MANIFEST.MF file in the main jar specifies those other jars. I just
repackaged things. If there's a switch you can flip to just make it
repackage, that's almost certainly better (mostly because it works).
On Thu, Apr 7,
I'm certain that we're not having this problem in this case. For one
thing, unpacking lucene into the 'main' part of the job jar makes this
problem go away.
On Thu, Apr 7, 2011 at 4:02 PM, Lance Norskog wrote:
> Sometimes the 'class not found' exception means that it found the
> named class, but
Sometimes the 'class not found' exception means that it found the
named class, but *that* class has missing dependencies. I haven't
learned how to distinguish "I can't find X" and "I can't find
dependencies for X".
On Thu, Apr 7, 2011 at 12:37 PM, Benson Margulies wrote:
> We've set up a hadoop j
We've set up a hadoop job jar file to do vectorization.
The structure we have is that our code, which is a single class with
the main function, is in the unpacked part of the jar file, and
mahout-core and its dependencies are in the lib directory of the jar
file.
The results are the following. In
