(I mean the latter. One .jar with no .jar files inside.) I think we should let this simmer a bit to see if anyone has more bright ideas. While we have a working solution (good) I dislike committing something that you find ugly.
On Mon, May 9, 2011 at 5:08 PM, Benson Margulies <[email protected]> wrote: > The term 'make one jar' is a bit ambiguous to me. If you mean, 'make > one job jar that has all the job classes in the unpacked parts and all > the dependencies in lib', fine. If you mean 'shade it all into one > giant jar without a lib', I'm slightly squeamish -- but there are > options in shade to assure that this works right, even given bouncy > castle or other things with SPIs if we have any to worry about.
