Require servlet and filter names.

This edges DW even closer to the Servlet 3 API.
Upgrade to Jetty 9.0.4.
Upgrade to Liquidbase 3.

Removed the "dump" command until someone cares.
Fix example config.
Upgraded Freemarker.
Upgraded Mustache.
Revert "Upgrade to Liquidbase 3."

This reverts commit e38ff426c54abaf714ac58edc2f31d0a53c96d92.
Adding a few pointers to the dropwizzard-example readme to nudge
folks into the right direction. (I'm assuming here that whoever
walks up the dw-example, they just want to see stuff work first
rather than trying to figure out the data format for a Person, etc)
Merge pull request #360 from ojilles/master

Small clarifications on the dw-example README
Update dependencies for mockito

Removed mockito-all artifact and replaced with independent artifacts
for hamcrest and objenesis
Upgrade HSQLDB.
Upgrade tomcat-jdbc.
Update Hamcrest and Objenesis to latest
Merge pull request #366 from mvolkhart/fixIssue364

Fix issue364
Generalize DropwizardAppRule

`DropwizardAppRule` uses reflection to invoke the nullary constructor of
the target `Application`. However, applications that don't define a
public nullary constructor cannot be used.

This affects all Scala Applications, because the app is defined as an
Object, (which has a private nullary constructor).

This will also affect apps that are parameterized in some way, or that
protect the nullary constructor (e.g. for Singletons).

By introducing a `newApplication()` method and providing the current,
reflection-based implementation as the default, users may override this
to provide instances of their application themselves.
Merge pull request #367 from nicktelford/feature/generalize-dropwizard-app-rule

Generalize DropwizardAppRule
First stab at more human configuration errors

    * `ConfigurationException` has been made abstract and broken out in
    to `ConfigurationParsingException` and
    `ConfigurationValidationException` to properly encapsulate the
    different kinds of errors.
    * `ConfigurationFactory` catches a variety of common Jackson and
    SnakeYAML `Exception` and attempts to turn them in to sane
    `ConfigurationParsingException`s.
    * When provided with _suggestions_, `ConfigurationParsingException`
    will provide the user with the top-5, fuzzy matched against their
    input by Levenshtein distance.
Suppress stack-traces for ConfigurationExceptions.

Stack-traces are for unexpected program errors. ConfigurationExceptions
are an expected consequence of an invalid runtime configuration.
Therefore, the stack-trace adds no information of value.

Lets suppress it so it's less likely to scare people.
Use H2, not HyperSQL for most things.
Remove docs for non-existent constructor parameter