Major Description
Need some kind of self-contained mechanism for running kafka to get around the following:
1) The location of the source checkout/build is not necessarily the same place where it will be running (the build location and that user's ivy cache dir) potentially leading to sync problems (forgetting the ivy dir) or just adding overhead to the deployment process (additional steps to remember introduces more chances for mistakes)
2) The user running the kafka service in a production setting may not even have a real home directory
Think something like a 'fat jar' packaging (something that contains all necessary jar versions in one convenient place) would simplify deployment and reduce the chance for error (only one lib package to worry about, and it contains everything needed) and would be a little more production friendly