Mavenizing this project

Hey Nicholas, 

I attempted to mavenize your project for pushing to [Sonatype's central repo](http://www.sonatype.org/central/participate) (fix for #15). I know you said you had no plans to convert to maven but it's been 3 years and the maven repo is definitely the go to place for java open source projects. There were a couple of things I wasn't sure about while converting your project given the structure of it:

+ Licence section in the pom.xml: I believe you're using the MIT license but I did not link to it directly
+ groupId: I just used what the top level java package was
+ jArgs is not in the central repo and it's discouraged to use things not uploaded to the central repo. I'm unclear if Sonatype has a hard fast rule about this. You may want to consider converting to use [commons-cli](http://commons.apache.org/proper/commons-cli) or something similar.
+ your build.xml produces two artifacts and it's typical with maven to only produce one per project (http://www.sonatype.com/people/2010/01/how-to-create-two-jars-from-one-project-and-why-you-shouldnt/)

Also, I'm no authority on managing a project in a maven repo but the [instructions on their site](https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide) are pretty straightforward.

Cheers!