Found auto-configuration class problems:
- org.springframework.boot.actuate.autoconfigure.amqp.RabbitHealthContributorAutoConfiguration:
- after 'org.springframework.boot.amqp.autoconfigure.RabbitAutoConfiguration' is from an optional dependency and should be declared in afterName
- org.springframework.boot.actuate.autoconfigure.metrics.amqp.RabbitMetricsAutoConfiguration:
- after 'org.springframework.boot.amqp.autoconfigure.RabbitAutoConfiguration' is from an optional dependency and should be declared in afterName
Update `ClientHttpConnectorAutoConfiguration` with a condition to ensure
that `ClientHttpConnectorBuilder.detect` will return a result. Prior
to this commit, when using a JDK without `java.net.http.HttpClient`
access the auto-configuration would fail.
Fixes gh-45955
Rework profile name validation logic so that `.` and `+` and `@` can
be used in the names. Also provide an opt-out property that can be
set to restore earlier Spring Boot behavior.
The commit also include an update to the reference documentation.
Fixes gh-45947
Previously, we called getCredentials() to determine whether or not a
repository requires authentication. Unfortunately, the method has the
unwanted side-effect of assigning empty username and password
credentials to a repository that previously did not require
authentication and did not, therefore, have any credentials. These
empty credentials can then cause subsequent failures because
"Username must not be null!".
There's no side-effect-free public API for accessing a repository's
credentials. Instead, we're using some internal API on
AuthenticationSupportedInternal. If this causes problems when
upgrading to a new version of Gradle a different approach will be
required. For example, we could pass in the repositories in two
separate collections: those that require authentication and those
that don't.
Closes gh-45950
