Releases: xvik/dropwizard-guicey
Releases Β· xvik/dropwizard-guicey
7.1.3
- Update to dropwizard 4.0.7
- Fix guicey ApplicationShutdownEvent typo (#387)
NOTE: If your code uses this event directly (name with typo: ApplicationShotdownEvent), then it would
be a breaking change and event name must be corrected manually in your code (to ApplicationShutdownEvent).
Sorry, can't do it in a backwards-compatible way, but I assume rare usage so should not affect many.
6.2.3
- Update to dropwizard 3.0.7
- Fix guicey ApplicationShutdownEvent typo (#387)
NOTE: If your code uses this event directly (name with typo: ApplicationShotdownEvent), then it would
be a breaking change and event name must be corrected manually in your code (to ApplicationShutdownEvent).
Sorry, can't do it in a backwards-compatible way, but I assume rare usage so should not affect many.
7.1.2
6.2.2
5.10.2
7.1.1
6.2.1
5.10.1
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
- inner jersey client creation is customizable now with TestClientFactory implementation
- 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)
- TestSupport.buildCommandRunner() - builds runner for command execution
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
- inner jersey client creation is customizable now with TestClientFactory implementation
- 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)
- TestSupport.buildCommandRunner() - builds runner for command execution