The MR project supports jars which have a subdirectory lib/ inside it, carrying all required dependencies. Would that not solve your need? You don't need to re-pack things, just pack them with the lib/ created inside with necessary dependencies during the build itself.
On Sun, Apr 21, 2013 at 12:43 PM, Vjeran Marcinko <vjeran.marci...@email.t-com.hr> wrote: > Hi, > > > > Can somebody tell me if there's some easy way to specify 3rd party libs for > my MR driver application without having to: > > > > 1. Create fat jar by unpackaging all dep libs and packing them again > (which really takes some time for couple of dozen dep libs wit my gradle > fatjar plugin task) > > 2. Specify libs individually inside „-libjars“ option for Tool – but > that's cumbersome since one has to specify each of them individually and > that means building this string somehow > > > > Isn't there some way to specify just some directory, say „libs“ on your > local drive, and place lib jars there, and driver configuration to pick them > up? Or just to pack all jars into one jar, but unlike fat jar which requires > unpacking every lib and packing them again, just to nest these jars inside > this new archive? > > > > Regards, > > Vjeran > > > > -- Harsh J
