With the ability to package configurations from their own Maven module it makes sense to move some of this code into those modules. For example, the command line parsing stuff can move into the module for the command line tool that is actually using it; same with logging setup so that it can be configured appropriately for client, server or plugin operation.
By moving the main entry point into the executable module itself it also gives it a chance to do what it needs to be done before bootstrapping the kernel. This would allow us to eliminate some of the static initialization blocks of the "make sure this runs first" type which are a little fragile.
-- Jeremy
