5.7.1-1

• [jdbi3]
  • Fix dropwizard 2.1.5 compatibility

5.7.0-1

• Add SBOM (json and xml with cyclonedx classifier)

5.6.1-1

• No changes, except BOM versions

5.6.0-1

• [gsp, spa]
  • Support new asset servlet behaviour (dw 2.1.0): direct status used instead of sendError when asset not found
  • Do not use sendError (in all cases), instead, just set response status (it allows all error responses
    modification in filters)

5.5.0-1

• New test modules, extracted from guicey core (preserving package):
  • guicey-test-junit4
  • guicey-test-spock

5.4.2-1

• No changes, except BOM versions

5.4.1-2

• [jdbi3]
  • Fix NPE on repository injection point (@Inject in interface) after .printGuiceAopMap() enabling
  • Support repository recognition from binding target: bind(Base.class).to(Repository.class) (where Repository extends Base)
    This is a very special case when repository "implementation" (actual queries) could be "pluggable"
    (e.g. jdbi repository implementation is only one type of possible implementation).

5.4.1-1

• No changes, except BOM versions

5.4.0-1

• Module poms use direct dependencies (without dependencyManagement section as before)
• BOM does not declare properties from guicey BOM anymore: dropwizard.version, guice.version and hk2.version
• [validation]
  • Add strictGroupsDeclaration() for ValidationBundle (avoid implicit Default group usage) (#69)
• Add guicey-jdbi3-jdk8 meta module (pom only) fixing jdbi3 dependencies for java8 compatibility

IMPORTANT: Since dropwizard 2.0.22 dropwizard-jdbi3 module requires java 11 or above
due to caffeine library upgrade (see caffeine author explanation)
(actually, new jdbi3 version depends on caffeine 3 while dropwizard itself still depends on caffeine 2).

To bring back java 8 compatibility you must manually force caffeine version:
implementation 'com.github.ben-manes.caffeine:caffeine:2.9.2'
Or just use new meta package guicey-jdbi3-jdk8, which fixes classpath for you.

0.7.1

Maintenance release for dropwizard 1.3

• Update to guicey 4.2.3
• Fix jdbi3 compatibility