mirror of
https://github.com/spring-projects/spring-boot.git
synced 2024-07-05 00:56:58 +08:00
Polish
See gh-39910
This commit is contained in:
parent
24218ac4a8
commit
412b8dd548
@ -35,7 +35,7 @@ import static org.assertj.core.api.Assertions.assertThat;
|
||||
*
|
||||
* @author Andy Wilkinson
|
||||
*/
|
||||
public class LiquibasePropertiesTests {
|
||||
class LiquibasePropertiesTests {
|
||||
|
||||
@Test
|
||||
void valuesOfShowSummaryMatchValuesOfUpdateSummaryEnum() {
|
||||
|
@ -1203,7 +1203,7 @@ The `info` endpoint publishes information about your Operating System, see {spri
|
||||
|
||||
[[actuator.endpoints.info.process-information]]
|
||||
==== Process Information
|
||||
The `info` endpoint publishes information about your process, see {spring-boot-module-api}/info/ProcessInfo.html[`Process`] for more details.
|
||||
The `info` endpoint publishes information about your process, see {spring-boot-module-api}/info/ProcessInfo.html[`ProcessInfo`] for more details.
|
||||
|
||||
|
||||
|
||||
|
@ -72,7 +72,7 @@ To learn more about ahead-of-time processing, please see the <<native-image#nati
|
||||
https://wiki.openjdk.org/display/crac/Main[Coordinated Restore at Checkpoint] (CRaC) is an OpenJDK project that defines a new Java API to allow you to checkpoint and restore an application on the HotSpot JVM.
|
||||
It is based on https://github.com/checkpoint-restore/criu[CRIU], a project that implements checkpoint/restore functionality on Linux.
|
||||
|
||||
The principle is the following: you start your application almost as usual but with a CRaC enabled version of the JDK like https://bell-sw.com/pages/downloads/?package=jdk-crac[Bellsoft Liberica JDK with CRaC] or https://www.azul.com/downloads/?package=jdk-crac#zulu[Azul Zulu JDK with CRaC].
|
||||
The principle is the following: you start your application almost as usual but with a CRaC enabled version of the JDK like https://bell-sw.com/pages/downloads/?package=jdk-crac[BellSoft Liberica JDK with CRaC] or https://www.azul.com/downloads/?package=jdk-crac#zulu[Azul Zulu JDK with CRaC].
|
||||
Then at some point, potentially after some workloads that will warm up your JVM by executing all common code paths, you trigger a checkpoint using an API call, a `jcmd` command, an HTTP endpoint, or a different mechanism.
|
||||
|
||||
A memory representation of the running JVM, including its warmness, is then serialized to disk, allowing a fast restoration at a later point, potentially on another machine with a similar operating system and CPU architecture.
|
||||
|
@ -80,7 +80,7 @@ When used to secure a client-side connection, a `truststore` is typically config
|
||||
[TIP]
|
||||
====
|
||||
PEM content can be used directly for both the `certificate` and `private-key` properties.
|
||||
If the property values contains `BEGIN` and `END` markers then they will be treated as PEM content rather than a resource location.
|
||||
If the property values contain `BEGIN` and `END` markers then they will be treated as PEM content rather than a resource location.
|
||||
|
||||
The following example shows how a truststore certificate can be defined:
|
||||
|
||||
|
@ -1055,7 +1055,7 @@ include::code:MyRedisConfiguration[]
|
||||
|
||||
Spring Boot can't tell from `GenericContainer` which container image is used, so the `name` attribute from `@ServiceConnection` must be used to provide that hint.
|
||||
|
||||
You can also can use the `name` attribute of `@ServiceConnection` to override which connection detail will be used, for example when using custom images.
|
||||
You can also use the `name` attribute of `@ServiceConnection` to override which connection detail will be used, for example when using custom images.
|
||||
If you are using the Docker image `registry.mycompany.com/mirror/myredis`, you'd use `@ServiceConnection(name="redis")` to ensure `RedisConnectionDetails` are created.
|
||||
|
||||
|
||||
|
@ -30,7 +30,7 @@ import org.springframework.boot.autoconfigure.ImportAutoConfiguration;
|
||||
* observability.
|
||||
* <p>
|
||||
* If this annotation is applied to a sliced test, an in-memory {@code MeterRegistry}, a
|
||||
* no-op {@code Tracer} and an {@code ObservationRegistry} is added to the application
|
||||
* no-op {@code Tracer} and an {@code ObservationRegistry} are added to the application
|
||||
* context.
|
||||
*
|
||||
* @author Moritz Halbritter
|
||||
|
@ -44,7 +44,7 @@ import static org.assertj.core.api.Assertions.assertThat;
|
||||
@DisabledIfDockerUnavailable
|
||||
@ExtendWith(OutputCaptureExtension.class)
|
||||
@ImportTestcontainers(Containers.class)
|
||||
public class TestContainersParallelStartupWithImportTestcontainersIntegrationTests {
|
||||
class TestContainersParallelStartupWithImportTestcontainersIntegrationTests {
|
||||
|
||||
@Test
|
||||
void startsInParallel(CapturedOutput out) {
|
||||
|
@ -113,7 +113,7 @@ class JarFileArchiveTests {
|
||||
URL url = urls.iterator().next();
|
||||
assertThat(url).isNotEqualTo(JarUrl.create(this.file, "nested.jar"));
|
||||
// The unpack URL must be a raw file URL (see gh-38833)
|
||||
assertThat(url.toString()).startsWith("file:").endsWith("/nested.jar").doesNotStartWith("jar:");
|
||||
assertThat(url.toString()).startsWith("file:").endsWith("/nested.jar");
|
||||
}
|
||||
|
||||
@Test
|
||||
|
@ -61,7 +61,7 @@ interface DataObjectBinder {
|
||||
* @param context the bind context
|
||||
* @param exception the exception about to be thrown
|
||||
*/
|
||||
default <T> void onUnableToCreateInstance(Bindable<T> target, Binder.Context context, RuntimeException exception) {
|
||||
default <T> void onUnableToCreateInstance(Bindable<T> target, Context context, RuntimeException exception) {
|
||||
}
|
||||
|
||||
}
|
||||
|
@ -39,7 +39,7 @@ class MissingParameterNamesFailureAnalyzer implements FailureAnalyzer {
|
||||
|
||||
static final String POSSIBILITY = "This may be due to missing parameter name information";
|
||||
|
||||
static String ACTION = """
|
||||
static final String ACTION = """
|
||||
Ensure that your compiler is configured to use the '-parameters' flag.
|
||||
You may need to update both your build tool settings as well as your IDE.
|
||||
(See https://github.com/spring-projects/spring-framework/wiki/Upgrading-to-Spring-Framework-6.x#parameter-name-retention)
|
||||
|
@ -104,7 +104,7 @@ public class Session {
|
||||
|
||||
/**
|
||||
* Session cookie properties. This class is provided only for back-compatibility
|
||||
* reasons, consider using {@link org.springframework.boot.web.server.Cookie} whever
|
||||
* reasons, consider using {@link org.springframework.boot.web.server.Cookie} whenever
|
||||
* possible.
|
||||
*/
|
||||
public static class Cookie extends org.springframework.boot.web.server.Cookie {
|
||||
@ -113,7 +113,7 @@ public class Session {
|
||||
|
||||
/**
|
||||
* Available session tracking modes (mirrors
|
||||
* {@link jakarta.servlet.SessionTrackingMode}.
|
||||
* {@link jakarta.servlet.SessionTrackingMode}).
|
||||
*/
|
||||
public enum SessionTrackingMode {
|
||||
|
||||
|
@ -69,16 +69,16 @@ org.springframework.boot.diagnostics.analyzer.BeanDefinitionOverrideFailureAnaly
|
||||
org.springframework.boot.diagnostics.analyzer.BeanNotOfRequiredTypeFailureAnalyzer,\
|
||||
org.springframework.boot.diagnostics.analyzer.BindFailureAnalyzer,\
|
||||
org.springframework.boot.diagnostics.analyzer.BindValidationFailureAnalyzer,\
|
||||
org.springframework.boot.diagnostics.analyzer.UnboundConfigurationPropertyFailureAnalyzer,\
|
||||
org.springframework.boot.diagnostics.analyzer.InvalidConfigurationPropertyNameFailureAnalyzer,\
|
||||
org.springframework.boot.diagnostics.analyzer.InvalidConfigurationPropertyValueFailureAnalyzer,\
|
||||
org.springframework.boot.diagnostics.analyzer.MissingParameterNamesFailureAnalyzer,\
|
||||
org.springframework.boot.diagnostics.analyzer.MutuallyExclusiveConfigurationPropertiesFailureAnalyzer,\
|
||||
org.springframework.boot.diagnostics.analyzer.NoSuchMethodFailureAnalyzer,\
|
||||
org.springframework.boot.diagnostics.analyzer.NoUniqueBeanDefinitionFailureAnalyzer,\
|
||||
org.springframework.boot.diagnostics.analyzer.PortInUseFailureAnalyzer,\
|
||||
org.springframework.boot.diagnostics.analyzer.ValidationExceptionFailureAnalyzer,\
|
||||
org.springframework.boot.diagnostics.analyzer.InvalidConfigurationPropertyNameFailureAnalyzer,\
|
||||
org.springframework.boot.diagnostics.analyzer.InvalidConfigurationPropertyValueFailureAnalyzer,\
|
||||
org.springframework.boot.diagnostics.analyzer.PatternParseFailureAnalyzer,\
|
||||
org.springframework.boot.diagnostics.analyzer.PortInUseFailureAnalyzer,\
|
||||
org.springframework.boot.diagnostics.analyzer.UnboundConfigurationPropertyFailureAnalyzer,\
|
||||
org.springframework.boot.diagnostics.analyzer.ValidationExceptionFailureAnalyzer,\
|
||||
org.springframework.boot.liquibase.LiquibaseChangelogMissingFailureAnalyzer,\
|
||||
org.springframework.boot.web.context.MissingWebServerFactoryBeanFailureAnalyzer,\
|
||||
org.springframework.boot.web.embedded.tomcat.ConnectorStartFailureAnalyzer
|
||||
|
@ -545,7 +545,7 @@ class JettyServletWebServerFactoryTests extends AbstractServletWebServerFactoryT
|
||||
}
|
||||
|
||||
@Test
|
||||
void shouldApplyingMaxConnectionUseConnector() throws Exception {
|
||||
void shouldApplyMaxConnectionsToConnectors() throws Exception {
|
||||
JettyServletWebServerFactory factory = getFactory();
|
||||
factory.setMaxConnections(1);
|
||||
this.webServer = factory.getWebServer();
|
||||
|
Loading…
Reference in New Issue
Block a user