Fix some doc anchors

See gh-22839
pull/22845/head
dreis2211 4 years ago committed by Stephane Nicoll
parent fcab5d6ce1
commit 11df8216ad

@ -2478,7 +2478,7 @@ Overriding versions may cause compatibility issues.
To override dependency versions with Maven, see {spring-boot-maven-plugin-docs}#using[this section] of the Maven plugin's documentation. To override dependency versions with Maven, see {spring-boot-maven-plugin-docs}#using[this section] of the Maven plugin's documentation.
To override dependency versions in Gradle, see {spring-boot-gradle-plugin-docs}#managing-dependencies-customizing[this section] of the Gradle plugin's documentation. To override dependency versions in Gradle, see {spring-boot-gradle-plugin-docs}#managing-dependencies-dependency-management-plugin-customizing[this section] of the Gradle plugin's documentation.

@ -633,7 +633,7 @@ You cannot use a wildcard in a `classpath:` location.
[[boot-features-external-config-files-profile-specific]] [[boot-features-external-config-files-profile-specific]]
==== Profile Specific Files[[boot-features-external-config-profile-specific-properties]] ==== Profile Specific Files
As well as `application` property files, Spring Boot will also attempt to load profile-specific files using the naming convention `application-\{profile}`. As well as `application` property files, Spring Boot will also attempt to load profile-specific files using the naming convention `application-\{profile}`.
For example, if your application activates a profile named `prod` and uses YAML files, then both `application.yml` and `application-prod.yml` will be considered. For example, if your application activates a profile named `prod` and uses YAML files, then both `application.yml` and `application-prod.yml` will be considered.

Loading…
Cancel
Save