Phillip Webb

We're going to look to see if we can improve the default behavior so that liveness and readiness groups have sensible memberships unless the user has specifically configured them otherwise....

WE discussed this as a team and decided that option 1 is the best way to go. We'd like to rename `ClientOptionsBuilderCustomizer` to `LettuceClientOptionsBuilderCustomizer`. We can take care of that...

All yours @itsAkshayDubey

Can you provide some more details of what you're looking for? We do already have some code in `OAuth2ResourceServerJwtConfiguration` which creates a `JwtDecoder`. Perhaps you can provide a sample application...

@hannah23280, We're discussing this again today and we wondered if you could provide a sample application that shows how you are currently configuring your beans. We want to make sure...

Thanks for the additional information. I'm not sure this pattern is generally applicable and something that will suit every application. As such, I don't think we'll be able to provide...

The test containers issue doesn't seem to be getting any traction as yet. I think we could change `TestcontainersLifecycleBeanPostProcessor.isReusedContainer` to do the same `TestcontainerConfiguration.getInstance().environmentSupportsReuse()` check. We can always change again...

@cpuzicha Do you have a way for us to replicate the "The task 'bootStartScripts' (org.gradle.jvm.application.tasks.CreateStartScripts) is not a subclass of the given type (org.gradle.api.tasks.application.CreateStartScripts)" error? I'm not sure we've seen...

We discussed this today as a team and we're not keen to change the default banner display. We feel it's better for `@SpringBootTest` to work as closely as possible to...

I wonder if we could put the application name in a logback variable then use ` property{APPLICATION_NAME}` in the console pattern.