5.10.1

• Update to dropwizard 2.1.11

7.1.0

• Update to dropwizard 4.0.4
• Add qualifier annotations support for configuration properties binding:
  any configuration property (any level), annotated with qualifier annotation, would be
  directly bound with that qualifier. Core dropwizard objects could be qualified on overridden getter
• Test improvements:
  • Junit 5 extensions could inject DropwizardTestSupport object itself as test method parameter
  • ClientSupport:
    • inner jersey client creation is customizable now with TestClientFactory implementation
      (new attribute "clientFactory" in @TestGuiceyApp and @TestDropwizardApp)
    • default factory would automatically configure:
      • multipart feature if available in classpath (dropwizard-forms)
      • direct console logging (to see requests and responses directly in console)
    • New methods:
      • basePathRoot - root url (only with port)
      • get(), post(), delete(), put() - simple shortcut methods to perform basic operations relative to server root
  • Context support object (DropwizardTestSupport) and client (ClientSupport) instances are accessible now statically
    for both manual run (TestSupport) and junit extensions: TestSupport.getContext() and TestSupport.getContextClient()
  • New generic builder for flexible DropwizardTestSupport object creation and run (when junit extension can't be used):
    TestSupport.builder() (with lifecycle listeners support)
  • TestSupport methods changes:
    • Creation and run methods updated with config override (strings) support
    • Add creation and run methods application class only (and optional overrides).
    • Run methods without callback now return RunResult containing all objects, required for validation (for example, to examine config)
    • Add captureOutput method to record console output for assertions
  • Commands test support:
    • TestSupport.buildCommandRunner() - builds runner for command execution
      with the same builder options as in generic builder (TestSupport.builder(); including same configuration)
      and user input support.
    • Could be used to test application startup fail (without using system mocks)

Full release notes

6.2.0

• Update to dropwizard 3.0.4
• Add jsr305 as direct dependency to simplify usage @javax.annotation.Nullable
  (annotation is required for guice when nullable value could be injected)
• Add qualifier annotations support for configuration properties binding:
  any configuration property (any level), annotated with qualifier annotation, would be
  directly bound with that qualifier. Core dropwizard objects could be qualified on overridden getter
• Test improvements:
  • Junit 5 extensions could inject DropwizardTestSupport object itself as test method parameter
  • ClientSupport:
    • inner jersey client creation is customizable now with TestClientFactory implementation
      (new attribute "clientFactory" in @TestGuiceyApp and @TestDropwizardApp)
    • default factory would automatically configure:
      • multipart feature if available in classpath (dropwizard-forms)
      • direct console logging (to see requests and responses directly in console)
    • New methods:
      • basePathRoot - root url (only with port)
      • get(), post(), delete(), put() - simple shortcut methods to perform basic operations relative to server root
  • Context support object (DropwizardTestSupport) and client (ClientSupport) instances are accessible now statically
    for both manual run (TestSupport) and junit extensions: TestSupport.getContext() and TestSupport.getContextClient()
  • New generic builder for flexible DropwizardTestSupport object creation and run (when junit extension can't be used):
    TestSupport.builder() (with lifecycle listeners support)
  • TestSupport methods changes:
    • Creation and run methods updated with config override (strings) support
    • Add creation and run methods application class only (and optional overrides).
    • Run methods without callback now return RunResult containing all objects, required for validation (for example, to examine config)
    • Add captureOutput method to record console output for assertions
  • Commands test support:
    • TestSupport.buildCommandRunner() - builds runner for command execution
      with the same builder options as in generic builder (TestSupport.builder(); including same configuration)
      and user input support.
    • Could be used to test application startup fail (without using system mocks)

Full release notes

5.10.0

• Update to dropwizard 2.1.10
• Add jsr305 as direct dependency to simplify usage @javax.annotation.Nullable
  (annotation is required for guice when nullable value could be injected)
• Add qualifier annotations support for configuration properties binding:
  any configuration property (any level), annotated with qualifier annotation, would be
  directly bound with that qualifier. Core dropwizard objects could be qualified on overridden getter
• Test improvements:
  • Junit 5 extensions could inject DropwizardTestSupport object itself as test method parameter
  • ClientSupport:
    • inner jersey client creation is customizable now with TestClientFactory implementation
      (new attribute "clientFactory" in @TestGuiceyApp and @TestDropwizardApp)
    • default factory would automatically configure:
      • multipart feature if available in classpath (dropwizard-forms)
      • direct console logging (to see requests and responses directly in console)
    • New methods:
      • basePathRoot - root url (only with port)
      • get(), post(), delete(), put() - simple shortcut methods to perform basic operations relative to server root
  • Context support object (DropwizardTestSupport) and client (ClientSupport) instances are accessible now statically
    for both manual run (TestSupport) and junit extensions: TestSupport.getContext() and TestSupport.getContextClient()
  • New generic builder for flexible DropwizardTestSupport object creation and run (when junit extension can't be used):
    TestSupport.builder() (with lifecycle listeners support)
  • TestSupport methods changes:
    • Creation and run methods updated with config override (strings) support
    • Add creation and run methods application class only (and optional overrides).
    • Run methods without callback now return RunResult containing all objects, required for validation (for example, to examine config)
    • Add captureOutput method to record console output for assertions
  • Commands test support:
    • TestSupport.buildCommandRunner() - builds runner for command execution
      with the same builder options as in generic builder (TestSupport.builder(); including same configuration)
      and user input support.
    • Could be used to test application startup fail (without using system mocks)

Full release notes

5.9.3

• Update to dropwizard 2.1.9

NOTE: dropwizard-jdbi3 drops java 8 support in gradle because it leaks (through metrics-jdbi3) jdbi3 3.43.1, compiled for java 11, so, for java 8 compatibility, you'll have to manually force the correct version:

    implementation ('org.jdbi:jdbi3-core') {
        version { strictly '3.39.1' }
    }

(example project)

7.0.2

• Update to dropwizard 4.0.2

6.1.2

• Update to dropwizard 3.0.2

5.9.2

• Update to dropwizard 2.1.8

7.0.1

• Update to dropwizard 4.0.1
• [jdbi]
  • Fix jdbi 3.39 compatibility
  • Avoid redundant transaction isolation level checks (extra queries) (#318)
• [gsp]
  • Fix redirection to error page after direct template rendering fails

6.1.1

• Update to dropwizard 3.0.1
• Add missed javax.inject dependency (guice 6 could work with both javax and jakarta)
• Fix BOM for MAVEN projects: incorrect jakarta.inject version was selected (#317)
• [jdbi]
  • Fix jdbi 3.39 compatibility
  • Avoid redundant transaction isolation level checks (extra queries) (#318)
• [gsp]
  • Fix redirection to error page after direct template rendering fails