Skip to content
This repository has been archived by the owner on Feb 1, 2021. It is now read-only.

Bump dropwizard-guicey from 4.1.0 to 5.1.0 #11

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot-preview[bot]
Copy link

Bumps dropwizard-guicey from 4.1.0 to 5.1.0.

Release notes

Sourced from dropwizard-guicey's releases.

5.1.0

  • Update guice to 4.2.3 (java 14 support)
  • Update to dropwizard 2.0.10
  • Add junit 5 extensions (#74). Works much like existing spock extensions:
  • Spock extensions updates:
    • Internally, use DropwizardTestSupport instead of deprecated junit 4 rules
    • New features (port features from junit 5 extensions):
      • @UseDropwizardApp got new configurations: randomPorts and restMapping
      • @UseGuiceyHooks deprecated: instead additional hooks may be declared in static test field
      • ClientSupport test field will be injected with client support object instance
  • Junit 4 rules deprecated GuiceyAppRule, StartupErrorRules
  • Fix parallel tests support: guice logs interception wasn't thread safe (#103)
  • Fix invalid Automatic-Module-Name to 'ru.vyarus.dropwizard.guicey' (#106)

5.0.1

  • Update to dropwizard 2.0.2 (address CVE-2020-5245)
  • Fix yaml bindings report rendering with values containing string format parameters like %s (#77)

5.0.0

  • Update to dropwizard 2.0.0
    • (breaking in jersey 2.26)
      • Jersey 2.26 introduces an abstraction for injection layer in order to get rid of hk2 direct usage. This allows complete hk2 avoidance in the future. Right now it means that all direct hk2 classes must be replaced by jersey abstractions (but still hk2 is the only production ready integration)
        • Jersey InjectionManager now bound to guice context instead of hk2 ServiceLocator (locator still can be retrieved from manager)
        • Rename HK2 mentions into jersey (because now jersey is not tied to hk2)
          • @HK2Managed renamed to @JerseyManaged
        • JerseyProviderInstaller (installs classes annotated with @Provider) changes:
          • ValueParamProvider detected instead of ValueFactoryProvider
          • Supplier detected instead Factory (Factory implementations are not recognized anymore!)
          • org.glassfish.jersey.internal.inject.InjectionResolver detected instead of org.glassfish.hk2.api.InjectionResolver
        • Jersey installers use org.glassfish.jersey.internal.inject.AbstractBinder instead of hk specific org.glassfish.hk2.utilities.binding.AbstractBinder
        • Mark all hk2-related methods and options as deprecated (to be removed in the next version)
      • Jersey 2.26 implements jax-rs 2.1 which forced it to change some of it's apis.
        • org.glassfish.jersey.server.AsyncContext binding used instead of org.glassfish.jersey.server.internal.process.AsyncContext
    • (breaking dw 2.0)
      • Deprecated Bundle usages replaced with ConfigurableBundle (in new dropwizard version Bundle extends ConfigurableBundle)
        • Guicey configuration scope ConfigSope.DropwizardBundle now use ConfigurableBundle class for marking guice bundle scope instead of Bundle
      • dropwizard-bom now includes only dropwizard modules. All 3rd party dependencies are moved to dropwizard-dependencies package. So you'll have to update two boms now in order to update dropwizard version.
    • Update hk2 guice-bridge to 2.6.1
  • (breaking) Guicey configuration and lifecycle changes:
    • GuiceyBundle contract and behaviour changed to match dropwizard lifecycle:
... (truncated)
Changelog

Sourced from dropwizard-guicey's changelog.

5.1.0 (2020-06-02)

  • Update guice to 4.2.3 (java 14 support)
  • Update to dropwizard 2.0.10
  • Add junit 5 extensions (#74). Works much like existing spock extensions:
  • Spock extensions updates:
    • Internally, use DropwizardTestSupport instead of deprecated junit 4 rules
    • New features (port features from junit 5 extensions):
      • @UseDropwizardApp got new configurations: randomPorts and restMapping
      • @UseGuiceyHooks deprecated: instead additional hooks may be declared in static test field
      • ClientSupport test field will be injected with client support object instance
  • Junit 4 rules deprecated GuiceyAppRule, StartupErrorRules
  • Fix parallel tests support: guice logs interception wasn't thread safe (#103)
  • Fix invalid Automatic-Module-Name to 'ru.vyarus.dropwizard.guicey' (#106)

5.0.1 (2020-03-13)

  • Update to dropwizard 2.0.2 (address CVE-2020-5245)
  • Fix yaml bindings report rendering with values containing string format parameters like %s (#77)

5.0.0 (2019-12-15)

  • Update to dropwizard 2.0.0
    • (breaking in jersey 2.26)
      • Jersey 2.26 introduces an abstraction for injection layer in order to get rid of hk2 direct usage. This allows complete hk2 avoidance in the future. Right now it means that all direct hk2 classes must be replaced by jersey abstractions (but still hk2 is the only production ready integration)
        • Jersey InjectionManager now bound to guice context instead of hk2 ServiceLocator (locator still can be retrieved from manager)
        • Rename HK2 mentions into jersey (because now jersey is not tied to hk2)
          • @HK2Managed renamed to @JerseyManaged
        • JerseyProviderInstaller (installs classes annotated with @Provider) changes:
          • ValueParamProvider detected instead of ValueFactoryProvider
          • Supplier detected instead Factory (Factory implementations are not recognized anymore!)
          • org.glassfish.jersey.internal.inject.InjectionResolver detected instead of org.glassfish.hk2.api.InjectionResolver
        • Jersey installers use org.glassfish.jersey.internal.inject.AbstractBinder instead of hk specific org.glassfish.hk2.utilities.binding.AbstractBinder
        • Mark all hk2-related methods and options as deprecated (to be removed in the next version)
      • Jersey 2.26 implements jax-rs 2.1 which forced it to change some of it's apis.
        • org.glassfish.jersey.server.AsyncContext binding used instead of org.glassfish.jersey.server.internal.process.AsyncContext
    • (breaking dw 2.0)
      • Deprecated Bundle usages replaced with ConfigurableBundle (in new dropwizard version Bundle extends ConfigurableBundle)
        • Guicey configuration scope ConfigSope.DropwizardBundle now use ConfigurableBundle class for marking guice bundle scope instead of Bundle
      • dropwizard-bom now includes only dropwizard modules. All 3rd party dependencies are moved to dropwizard-dependencies package. So you'll have to update two boms now in order to update dropwizard version.
    • Update hk2 guice-bridge to 2.6.1
  • (breaking) Guicey configuration and lifecycle changes:
    • GuiceyBundle contract and behaviour changed to match dropwizard lifecycle:
... (truncated)
Commits
  • ada2028 [Gradle Release Plugin] - pre tag commit: '5.1.0'.
  • 00d486f fix javadoc
  • c9e47a7 update gsp doc (custom class loader case)
  • 7e3c669 update docs
  • 1062f5a update docs for new version
  • 86e2831 update release-notes section in docs
  • b29a44e update testing sections in docs
  • 9e9934a support qualified and parameterized parameters injection in junit5 extensions
  • 2879085 remove junit5 extension special param injection cases covered covered by inje...
  • 25bd572 junit5 injection scope test
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Jun 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants