The assertion in AllEnginesAutoConfigurationTest has been changed to use containsExactlyInAnyOrder since the order there isn't important, and it seems like the beans are created in a different order now.
The AppEngineConfiguration is going to anyways order all the available contributors before applying them. The configurators are only the ones that have been registered during bean registration.
Our Spring Kafka integration has been adapted to use the new SameIntervalTopicReuseStrategy instead of the deprecated (in 3.0) and removed (in 3.1) spring-kafka FixedDelayStrategy. It is the same thing, just named differently for clarification reasons by the Spring Kafka team.
We have also added spring-context as a test dependency in flowable-http , because the SpringWebClientFlowableHttpClient is using ReactorClientHttpConnector from spring-web, which since Spring Framework 6.1 is implementing SmartLifecycle and thus needs spring-context
The following dependencies have been upgraded:
The assertion in
AllEnginesAutoConfigurationTest
has been changed to usecontainsExactlyInAnyOrder
since the order there isn't important, and it seems like the beans are created in a different order now. TheAppEngineConfiguration
is going to anyways order all the available contributors before applying them. The configurators are only the ones that have been registered during bean registration.Our Spring Kafka integration has been adapted to use the new
SameIntervalTopicReuseStrategy
instead of the deprecated (in 3.0) and removed (in 3.1) spring-kafkaFixedDelayStrategy
. It is the same thing, just named differently for clarification reasons by the Spring Kafka team.We have also added
spring-context
as a test dependency inflowable-http
, because theSpringWebClientFlowableHttpClient
is usingReactorClientHttpConnector
fromspring-web
, which since Spring Framework 6.1 is implementingSmartLifecycle
and thus needs spring-context