This commit removes support for the following properties that are
deprecated since Spring Boot 2.4:
- logging.pattern.rolling-file-name
- logging.file.clean-history-on-start
- logging.file.max-size
- logging.file.total-size-cap
- logging.file.max-history
Closes gh-48489
* pr/48347:
Polish "Use Charset instead of String for Mustache templates support"
Use Charset instead of String for Mustache templates support
Closes gh-48347
The MustacheResourceTemplateLoader previously defined the template
encoding as a String, defaulting to "UTF-8". This change replaces the
field with a Charset and initializes it with StandardCharsets.UTF_8.
Using Charset improves type safety and aligns with modern Spring Boot
standards, while avoiding implicit charset lookup issues.
See gh-48347
Signed-off-by: djlee <ddongjunn@gmail.com>
This commit auto-configures the following beans with their corresponding
conventions, when available:
- ProcessorMetrics with JvmCpuMeterConventions
- JvmMemoryMetrics with JvmMemoryMeterConventions
- JvmThreadMetrics with JvmThreadMeterConventions
- ClassLoaderMetrics with JvmClassLoadingMeterConventions
See gh-47935
Signed-off-by: Dmytro Nosan <dimanosan@gmail.com>
This commit introduces a failure analyzer implementation that provides
actionable guidance when Testcontainers fails to detect a running
Docker-compatible environment.
See gh-47797
Signed-off-by: Dmytro Nosan <dimanosan@gmail.com>
* pr/47716:
Polish "Add support for configuring SimpleMessageListenerContainer"
Add support for configuring SimpleMessageListenerContainer
Closes gh-47716
This commit introduces a `SimpleJmsListenerContainerFactoryConfigurer`
that can be used to conveniently apply settings provided
by JMS auto-configuration to `SimpleJmsListenerContainerFactory`
instances.
See gh-47716
Signed-off-by: Vedran Pavic <vedran@vedranpavic.com>
* pr/46766:
Polish "Decorate all Assert implementations with @CheckReturnValue"
Decorate all Assert implementations with @CheckReturnValue
Closes gh-46766
This commit updates the reference documentation to better reflect
changes applied in gh-48310. As of Spring Boot 4.0.1,
`HttpMessageConverter` beans are all considered as "custom" converters
and will be set ahead of the converters list in the auto-configuration
support.
For more specific changes, developers should contribute
`ClientHttpMessageConvertersCustomizer` or
`ServerHttpMessageConvertersCustomizer` beans to better reflect their
intent: should the converter be configured for client, server or both?
How should this converter be used?
Previously, Spring Boot was relying on heuristics but they would cause
issues for server-only converters, or for specific configuration that
were not meant to replace the default converter for a given media type.
Closes gh-48574
Phillip Webb
Stéphane Nicoll
Andy Wilkinson
CatiaCorreia
djlee
Moritz Halbritter
Dmytro Nosan
Lansana DIOMANDE
Vedran Pavic
Stefano Cordio
jwalter
Brian Clozel