Add Maven Archetypes for skeleton projects

It's a good idea to have a template for new projects to help users
adhere to best practices for project layout.

Provides:

  * A Java Archetype, `java-simple`, for creating new Java Dropwizard
  projects.
  * A Scala Archetype, `scala-simple`, for creating new Scala Dropwizard
  projects.
  * A utility, `dropwizard-create`, for bootstrapping a new project
  using the Archetypes.

The POM for generated projects will:

  * Generate JavaDoc/ScalaDoc, and build an attached doc JAR.
  * Build and attach a source JAR.
  * Build shaded JAR (optional)
  * Build an executable JAR for the Service.
  * Generate Maven Site

The `dropwizard-create` utility is provided so that users don't have to
grapple with Mavens' appalling UI for generating projects from
Archetypes. It ensures that all the necessary properties are provided to
the Archetypes and provides some sensible defaults for the lazy.
Merge branch 'master' into feature/maven-archetypes
Update archetype POM versions to latest

Keep things in sync with Dropwizard until merged.
Fix incorrect version variables

Both archetypes were generating POMs without resolving values for
`dropwizard.version` or `scala.version` (in the case of `scala-simple`).

We should use the current project version as the `dropwizard.version`
for generated projects, and `2.9.1` for the `scala.version` of Scala
projects.
Use incremental compiler for Scala projects

For Scala projects, we should use the Zinc incremental compiler. If a
Zinc server is currently running (on the default port) it will be used
automatically to further improve compile speed.
Update scala archetype to scala-maven-plugin 3.1.0
Merge branch 'master' into feature/maven-archetypes
Update Maven Archetypes for Dropwizard 0.6.0

Synchronises version POM numbers with upstream change.
Remove weird resource blocks in archetype POMs

These sections serve no purpose other than add confusion. Must have been
smoking something strange at the time.
Made dropwizard-create a filtered resource

The project version is now adopted from the project POM, rather than
being hand-coded. The script is built as part of the project's _package_
phase.

To install the script, build the project and put it on your PATH:

    $ mvn package
    $ cp ./dropwizard-archetypes/target/classes/dropwizard-create \
      /usr/local/bin/

This will ensure the script defaults to the current project version.
Fix incorrect version for dropwizard-create

When asked to print the program version (using the `--version` option)
`dropwizard-create` was printing the default generated project version
(_0.1.0-SNAPSHOT_) instead of the Dropwizard version.
Merge branch 'master' into feature/maven-archetypes
Cleanup Scala Service initialization

Now that Bundles can hook in to the Bootstrap process, we can move all
the Scala customizations from `ScalaService` to `ScalaBundle`.

`ScalaService` remains solely to provide the default `main` method for
Scala Services.
Support adding initialized providers to ResourceTest.
Expose JerseyTest via a getter.

Closes #192.
Merge pull request #191 from nicktelford/fix/scala-bundle-init

Cleanup Scala Service initialization
Merge branch 'feature/maven-archetypes' of github.com:nicktelford/dropwizard