One Jar To Rule Them All

[James M Snell]

Currently we ship lots of jars.  Despite being somewhat confusing, this 
can be a really good thing because it allows developers to pick and 
choose subsets of functions/features they wish to ship.  It does, 
however, make it more difficult when you really do want everything.

Therefore... I'm thinking about updating the build to produce a single 
all-inclusive jar in addition to the individual jars we currently have.

Any objections?

- James