Ported build over to Gradle

[ghost]

Hello! Some of us here at Puppet Labs are using ci-eye for our build radiators and I'd like to start extending its functionality a bit, but before I do that I'd really like to use a modern build system. This PR converts the build to gradle and the following commands will be the ones a person would need for development:

gradle test - Run the unit tests
gradle fatJar - Build the fat jar and place it in the ./build/lib directory.
gradle idea - Generate Idea project files.
gradle eclipse - Generate Eclipse project files.

Note that with a modern version of Idea, instead of running gradle idea, you can actually just open the gradle.build file directly and the project will be opened.

[scarytom]

Sadly, when Gradle generates the eclipse .project file, it doesn't generate the filter rules, and when it generates the eclipse .classpath file, it doesn't generate the access rules. Do you have any way to correct this?

[ghost]

Hmm, well I will look around for some way around this. If I can't find any way to do this I will remove that commit from this PR.

[ghost]

@scarytom, What I ended up doing was leaving the Eclipse .project and .settings/ directory. The Gradle Eclipse plugin will now append a couple things to them, if necessary, but leave everything else intact. The only thing that's generated from scratch is the .classpath file (the most important part of the Gradleizing) which now has the proper filter applied.