Steffen Nießing

Hi @ericdevries. Thanks for reporting this! An integration test creates a new `Application`. In the constructor of this class the `bootstrapLogging()` method gets invoked, which changes the logback configuration according...

Hi @volnikh. Thanks for reporting this! I'm not aware of a security issue on this topic. The `dropwizard-jdbi3` module also provides database access and there the `ManagedDataSource` [gets added to...

Hi @erik-sab. Adding the `ManagedDataSource` additionally to the `LifecycleEnvironment` would lead to multiple calls of the `start()` and `stop()` methods. We could change the access modifier of the `SessionFactoryManager#getDataSource()` method...

Fixed with #5681

@joschi is this still needed? It would be good to have up-to-date and clear docs, but I wonder, if we should now modify the migration guide for 2.0.x as this...

That one isn't that problematic IMO. Jersey 3.1.0 should be already released, we'll see when it's out.

The [roadmap](https://github.com/eclipse-ee4j/jersey/wiki/Road-Map#planned) of the Jersey project states the release to be planned for may.

The wiki has been updated and Jersey 3.1.0 is slated for september. If the release would be delivered this month, I think we can wait for it.

Jersey 3.1.0 finally appeared in Maven central.

Hi @wilbertpol, thanks for your contribution! Unfortunately, I'm not quite sure, if we can integrate this PR into Dropwizard 2.x. Users _could_ have sensitive information in their query parameters that...