Ah right, that was the gotcha. Well, as it happens, there are no such dependencies for Mahout at the moment. Those that really have to roll their own .jar can use the Mahout .jar instead of job file to construct something like this.
In the meantime Jake is right that we have a pretty immediate problem -- the job file doesn't work. I guess few people ever use it directly but I can say I saw the same thing. And we have a working solution -- just use Maven's deafult packaging logic, which re-jars stuff. I'll make a JIRA to say yea or nay to with a patch. On Mon, May 9, 2011 at 5:55 AM, Dmitriy Lyubimov <[email protected]> wrote: > One solution is to use shade plugin or similar technique to create one > job jar with all dependencies in it. Which i deem as a bad bractice, > because it unjars existing dependencies jar, and it breaks things on > occasion (e.g. if one of dependencies is a signed jar, such as > BouncyCastle). Projects get into using shade plugin only to require > major retrofit when they hit dependency like this.
