Issue 2

    Added a groovy-gradle template that sets up a basic project that includes
    questioning the user for values and file filtering.

    Added integrated tests to verify the LazyBonesScript works against the
    groovy-gradle template.

    Added improvements to AbstractFunctionalSpec so it can accept inputs to
    a lazybones script call

    Squashed various bugs in LazyBonesScript

    Added LazyBonesScript to LazyBonesMain

    task integTests runs installTemplates to make template tests easier
Issue 2 Post processing script

Fixed all formatting to comply with the formatting guide

changed the basic groovy app template

added info about the post processing script to the README
migrated the unit test to spock, fixed the name
Add commit message guidelines to CONTRIBUTING.md
Tweak some formatting, naming, and other similar things.
Missing from previous.
Make groovy-app's 'group' property conditional.

When users create a new project based on the `groovy-app` template, they may
not provide a value for the project's group ID. If that's the case, the
installed build.gradle file no longer includes the `group` property.
Merge branch 'tbarker'
Add example post install script to README.
Added groovy config slurper for configurable repos

You can now specify a list of bintray repositories to read from. In
~/.lazybones/config.groovy add a line like this:

bintrayRepositories = [
   "kyleboon/lazybones",
   "pledbrook/lazybones-templates"
]

which will allow you to use templates from either repository.
Repositories listed first are higher priority. if 'some-template' exists
in both repositories, it will use the one in the first repository
listed.

list, info and create were all updated to work with multiple
repositories.

If no configuration file is present then the application will use a
default configuration that points to 'pledbrook/lazybones-templates'.