5.2.0

• Update to dropwizard 2.0.16
• Remove direct usages of logback-classic classes to unlock logger switching (#127)
• Fix stackoverflow on config introspection caused by EnumMap fields (#87)
• Prioritize registered jersey provider extensions and add support for @Priority annotation (#97)
  Unifies raw dropwizard and guicey behavior. Possibly breaking, see note below.
• Add lifecycle event: ApplicationStoppedEvent (triggered on jersey lifecycle stop)

NOTE:
In raw dropwizard registered jersey extension (with environment.jersey().register(MyExceptionMapper.class))
is implicitly qualified as @Custom and always used in priority comparing to default dropwizard providers.

Before, guicey was registering provider extensions without this qualifier and so the default
dropwizard providers were used in priority (as registered earlier).
For example, it was impossible to register ExceptionMapper<Throwable> because dropwizard already registered one.
Now your custom mapper will be used in priority and so it is possible to override the default ExceptionMapper<Throwable>
(for example).

This COULD (unlikely, but still) change application behavior: your custom provider could be called in more cases.
But, as this behavior is the default for raw dropwizard, the change considered as a bugfix.
In case of problems, you could revert to legacy guicey behaviour with:
.option(InstallerOptions.PrioritizeJerseyExtensions, false)