Rationalize reference documentation anchors

Closes gh-26296

Author: philwebb

spring-boot-project/spring-boot-docs/src/docs/asciidoc/anchor-rewrite.properties

@@ -7,103 +7,103 @@ include::attributes.adoc[]
 Various properties can be specified inside your `application.properties` file, inside your `application.yml` file, or as command line switches.
 This appendix provides a list of common Spring Boot properties and references to the underlying classes that consume them.
 
-TIP: Spring Boot provides various conversion mechanism with advanced value formatting, make sure to review <<spring-boot-features.adoc#boot-features-external-config-conversion, the properties conversion section>>.
+TIP: Spring Boot provides various conversion mechanism with advanced value formatting, make sure to review <<spring-boot-features.adoc#features.external-config.typesafe-configuration-properties.conversion, the properties conversion section>>.
 
 NOTE: Property contributions can come from additional jar files on your classpath, so you should not consider this an exhaustive list.
 Also, you can define your own properties.
 
 
 
-[[common-application-properties-core]]
+[[common-application-properties.core]]
 == Core Properties [[core-properties]]
 include::config-docs/core.adoc[]
 
 
 
-[[common-application-properties-cache]]
+[[common-application-properties.cache]]
 == Cache Properties [[cache-properties]]
 include::config-docs/cache.adoc[]
 
 
 
-[[common-application-properties-mail]]
+[[common-application-properties.mail]]
 == Mail Properties [[mail-properties]]
 include::config-docs/mail.adoc[]
 
 
 
-[[common-application-properties-json]]
+[[common-application-properties.json]]
 == JSON Properties [[json-properties]]
 include::config-docs/json.adoc[]
 
 
 
-[[common-application-properties-data]]
+[[common-application-properties.data]]
 == Data Properties [[data-properties]]
 include::config-docs/data.adoc[]
 
 
 
-[[common-application-properties-transaction]]
+[[common-application-properties.transaction]]
 == Transaction Properties [[transaction-properties]]
 include::config-docs/transaction.adoc[]
 
 
 
-[[common-application-properties-data-migration]]
+[[common-application-properties.data-migration]]
 == Data Migration Properties [[data-migration-properties]]
 include::config-docs/data-migration.adoc[]
 
 
 
-[[common-application-properties-integration]]
+[[common-application-properties.integration]]
 == Integration Properties [[integration-properties]]
 include::config-docs/integration.adoc[]
 
 
 
-[[common-application-properties-web]]
+[[common-application-properties.web]]
 == Web Properties [[web-properties]]
 include::config-docs/web.adoc[]
 
 
 
-[[common-application-properties-templating]]
+[[common-application-properties.templating]]
 == Templating Properties [[templating-properties]]
 include::config-docs/templating.adoc[]
 
 
 
-[[common-application-properties-server]]
+[[common-application-properties.server]]
 == Server Properties [[server-properties]]
 include::config-docs/server.adoc[]
 
 
 
-[[common-application-properties-security]]
+[[common-application-properties.security]]
 == Security Properties [[security-properties]]
 include::config-docs/security.adoc[]
 
 
 
-[[common-application-properties-rsocket]]
+[[common-application-properties.rsocket]]
 == RSocket Properties [[rsocket-properties]]
 include::config-docs/rsocket.adoc[]
 
 
 
-[[common-application-properties-actuator]]
+[[common-application-properties.actuator]]
 == Actuator Properties [[actuator-properties]]
 include::config-docs/actuator.adoc[]
 
 
 
-[[common-application-properties-devtools]]
+[[common-application-properties.devtools]]
 == Devtools Properties [[devtools-properties]]
 include::config-docs/devtools.adoc[]
 
 
 
-[[common-application-properties-testing]]
+[[common-application-properties.testing]]
 == Testing Properties [[testing-properties]]
 include::config-docs/testing.adoc[]

spring-boot-project/spring-boot-docs/src/docs/asciidoc/appendix-application-properties.adoc

@@ -9,15 +9,15 @@ Remember to also look at the conditions report in your application for more deta
 
 
 
-[[auto-configuration-classes-from-autoconfigure-module]]
+[[auto-configuration-classes.core]]
 == spring-boot-autoconfigure
 The following auto-configuration classes are from the `spring-boot-autoconfigure` module:
 
 include::auto-configuration-classes/spring-boot-autoconfigure.adoc[]
 
 
 
-[[auto-configuration-classes-from-actuator]]
+[[auto-configuration-classes.actuator]]
 == spring-boot-actuator-autoconfigure
 The following auto-configuration classes are from the `spring-boot-actuator-autoconfigure` module:
 

spring-boot-project/spring-boot-docs/src/docs/asciidoc/appendix-auto-configuration-classes.adoc

@@ -7,11 +7,11 @@ Spring Boot jars include metadata files that provide details of all supported co
 The files are designed to let IDE developers offer contextual help and "`code completion`" as users are working with `application.properties` or `application.yml` files.
 
 The majority of the metadata file is generated automatically at compile time by processing all items annotated with `@ConfigurationProperties`.
-However, it is possible to <<configuration-metadata-additional-metadata,write part of the metadata manually>> for corner cases or more advanced use cases.
+However, it is possible to <<configuration-metadata.annotation-processor.adding-additional-metadata,write part of the metadata manually>> for corner cases or more advanced use cases.
 
 
 
-[[configuration-metadata-format]]
+[[configuration-metadata.format]]
 == Metadata Format
 Configuration metadata files are located inside jars under `META-INF/spring-configuration-metadata.json`.
 They use a JSON format with items categorized under either "`groups`" or "`properties`" and additional values hints categorized under "hints", as shown in the following example:
@@ -98,7 +98,7 @@ For example, when a developer is configuring the configprop:spring.jpa.hibernate
 
 
 
-[[configuration-metadata-group-attributes]]
+[[configuration-metadata.format.group]]
 === Group Attributes
 The JSON object contained in the `groups` array can contain the attributes shown in the following table:
 
@@ -139,7 +139,7 @@ The JSON object contained in the `groups` array can contain the attributes shown
 
 
 
-[[configuration-metadata-property-attributes]]
+[[configuration-metadata.format.property]]
 === Property Attributes
 The JSON object contained in the `properties` array can contain the attributes described in the following table:
 
@@ -254,7 +254,7 @@ Doing so is particularly useful when a `replacement` is provided.
 
 
 
-[[configuration-metadata-hints-attributes]]
+[[configuration-metadata.format.hints]]
 === Hint Attributes
 The JSON object contained in the `hints` array can contain the attributes shown in the following table:
 
@@ -317,15 +317,15 @@ The JSON object contained in the `providers` attribute of each `hint` element ca
 
 
 
-[[configuration-metadata-repeated-items]]
+[[configuration-metadata.format.repeated-items]]
 === Repeated Metadata Items
 Objects with the same "`property`" and "`group`" name can appear multiple times within a metadata file.
 For example, you could bind two separate classes to the same prefix, with each having potentially overlapping property names.
 While the same names appearing in the metadata multiple times should not be common, consumers of metadata should take care to ensure that they support it.
 
 
 
-[[configuration-metadata-providing-manual-hints]]
+[[configuration-metadata.manual-hints]]
 == Providing Manual Hints
 To improve the user experience and further assist the user in configuring a given property, you can provide additional metadata that:
 
@@ -334,10 +334,10 @@ To improve the user experience and further assist the user in configuring a give
 
 
 
-[[configuration-metadata-providing-manual-hints-value-hint]]
+[[configuration-metadata.manual-hints.value-hint]]
 === Value Hint
 The `name` attribute of each hint refers to the `name` of a property.
-In the <<configuration-metadata-format,initial example shown earlier>>, we provide five values for the `spring.jpa.hibernate.ddl-auto` property: `none`, `validate`, `update`, `create`, and `create-drop`.
+In the <<configuration-metadata.format,initial example shown earlier>>, we provide five values for the `spring.jpa.hibernate.ddl-auto` property: `none`, `validate`, `update`, `create`, and `create-drop`.
 Each value may have a description as well.
 
 If your property is of type `Map`, you can provide hints for both the keys and the values (but not for the map itself).
@@ -356,7 +356,7 @@ Assume a `sample.contexts` maps magic `String` values to an integer, as shown in
 ----
 
 The magic values are (in this example) are `sample1` and `sample2`.
-In order to offer additional content assistance for the keys, you could add the following JSON to <<configuration-metadata-additional-metadata,the manual metadata of the module>>:
+In order to offer additional content assistance for the keys, you could add the following JSON to <<configuration-metadata.annotation-processor.adding-additional-metadata,the manual metadata of the module>>:
 
 [source,json,indent=0]
 ----
@@ -380,7 +380,7 @@ If your IDE supports it, this is by far the most effective approach to auto-comp
 
 
 
-[[configuration-metadata-providing-manual-hints-value-providers]]
+[[configuration-metadata.manual-hints.value-providers]]
 === Value Providers
 Providers are a powerful way to attach semantics to a property.
 In this section, we define the official providers that you can use for your own hints.
@@ -407,7 +407,7 @@ The following table summarizes the list of supported providers:
 | Handles the property as if it were defined by the type defined by the mandatory `target` parameter.
 
 | `logger-name`
-| Auto-completes valid logger names and <<spring-boot-features.adoc#boot-features-custom-log-groups,logger groups>>.
+| Auto-completes valid logger names and <<spring-boot-features.adoc#features.logging.log-groups,logger groups>>.
   Typically, package and class names available in the current project can be auto-completed as well as defined groups.
 
 | `spring-bean-reference`
@@ -424,7 +424,7 @@ If no provider for a given property is supported, no special content assistance
 
 
 
-[[configuration-metadata-providing-manual-hints-any]]
+[[configuration-metadata.manual-hints.value-providers.any]]
 ==== Any
 The special **any** provider value permits any additional values to be provided.
 Regular value validation based on the property type should be applied if this is supported.
@@ -459,7 +459,7 @@ Note that, in the preceding example, any other value is also allowed.
 
 
 
-[[configuration-metadata-providing-manual-hints-class-reference]]
+[[configuration-metadata.manual-hints.value-providers.class-reference]]
 ==== Class Reference
 The **class-reference** provider auto-completes classes available in the project.
 This provider supports the following parameters:
@@ -503,7 +503,7 @@ The following metadata snippet corresponds to the standard `server.servlet.jsp.c
 
 
 
-[[configuration-metadata-providing-manual-hints-handle-as]]
+[[configuration-metadata.manual-hints.value-providers.handle-as]]
 ==== Handle As
 The **handle-as** provider lets you substitute the type of the property to a more high-level type.
 This typically happens when the property has a `java.lang.String` type, because you do not want your configuration classes to rely on classes that may not be on the classpath.
@@ -553,9 +553,9 @@ It is actually used internally as a `org.springframework.core.io.Resource` but c
 
 
 
-[[configuration-metadata-providing-manual-hints-logger-name]]
+[[configuration-metadata.manual-hints.value-providers.logger-name]]
 ==== Logger Name
-The **logger-name** provider auto-completes valid logger names and <<spring-boot-features.adoc#boot-features-custom-log-groups,logger groups>>.
+The **logger-name** provider auto-completes valid logger names and <<spring-boot-features.adoc#features.logging.log-groups,logger groups>>.
 Typically, package and class names available in the current project can be auto-completed.
 If groups are enabled (default) and if a custom logger group is identified in the configuration, auto-completion for it should be provided.
 Specific frameworks may have extra magic logger names that can be supported as well.
@@ -640,7 +640,7 @@ As Spring Boot defines a few logger groups out-of-the-box, dedicated value hints
 
 
 
-[[configuration-metadata-providing-manual-hints-spring-bean-reference]]
+[[configuration-metadata.manual-hints.value-providers.spring-bean-reference]]
 ==== Spring Bean Reference
 The **spring-bean-reference** provider auto-completes the beans that are defined in the configuration of the current project.
 This provider supports the following parameters:
@@ -680,7 +680,7 @@ If you provide that hint, you still need to transform the bean name into an actu
 
 
 
-[[configuration-metadata-providing-manual-hints-spring-profile-name]]
+[[configuration-metadata.manual-hints.value-providers.spring-profile-name]]
 ==== Spring Profile Name
 The **spring-profile-name** provider auto-completes the Spring profiles that are defined in the configuration of the current project.
 
@@ -702,14 +702,14 @@ The following metadata snippet corresponds to the standard `spring.profiles.acti
 
 
 
-[[configuration-metadata-annotation-processor]]
+[[configuration-metadata.annotation-processor]]
 == Generating Your Own Metadata by Using the Annotation Processor
 You can easily generate your own configuration metadata file from items annotated with `@ConfigurationProperties` by using the `spring-boot-configuration-processor` jar.
 The jar includes a Java annotation processor which is invoked as your project is compiled.
 
 
 
-[[configuration-metadata-annotation-processor-setup]]
+[[configuration-metadata.annotation-processor.configuring]]
 === Configuring the Annotation Processor
 To use the processor, include a dependency on `spring-boot-configuration-processor`.
 
@@ -763,7 +763,7 @@ You could also let the AspectJ plugin run all the processing and disable annotat
 
 
 
-[[configuration-metadata-annotation-processor-metadata-generation]]
+[[configuration-metadata.annotation-processor.automatic-metadata-generation]]
 === Automatic Metadata Generation
 The processor picks up both classes and methods that are annotated with `@ConfigurationProperties`.
 
@@ -807,7 +807,7 @@ The annotation processor applies a number of heuristics to extract the default v
 Default values have to be provided statically. In particular, do not refer to a constant defined in another class.
 Also, the annotation processor cannot auto-detect default values for ``Enum``s and ``Collections``s.
 
-For cases where the default value could not be detected, <<configuration-metadata-additional-metadata,manual metadata>> should be provided.
+For cases where the default value could not be detected, <<configuration-metadata.annotation-processor.adding-additional-metadata,manual metadata>> should be provided.
 Consider the following example:
 
 [source,java,pending-extract=true,indent=0,subs="verbatim,quotes,attributes"]
@@ -831,7 +831,7 @@ Consider the following example:
 	}
 ----
 
-In order to document default values for properties in the class above, you could add the following content to <<configuration-metadata-additional-metadata,the manual metadata of the module>>:
+In order to document default values for properties in the class above, you could add the following content to <<configuration-metadata.annotation-processor.adding-additional-metadata,the manual metadata of the module>>:
 
 [source,json,indent=0]
 ----
@@ -851,7 +851,7 @@ NOTE: Only the `name` of the property is required to document additional metadat
 
 
 
-[[configuration-metadata-annotation-processor-metadata-generation-nested]]
+[[configuration-metadata.annotation-processor.automatic-metadata-generation.nested-properties]]
 ==== Nested Properties
 The annotation processor automatically considers inner classes as nested properties.
 Rather than documenting the `ip` and `port` at the root of the namespace, we could create a sub-namespace for it.
@@ -888,7 +888,7 @@ TIP: This has no effect on collections and maps, as those types are automaticall
 
 
 
-[[configuration-metadata-additional-metadata]]
+[[configuration-metadata.annotation-processor.adding-additional-metadata]]
 === Adding Additional Metadata
 Spring Boot's configuration file handling is quite flexible, and it is often the case that properties may exist that are not bound to a `@ConfigurationProperties` bean.
 You may also need to tune some attributes of an existing key.

spring-boot-project/spring-boot-docs/src/docs/asciidoc/appendix-configuration-metadata.adoc

@@ -7,7 +7,7 @@ This appendix provides details of the dependencies that are managed by Spring Bo
 
 
 
-[[dependency-versions-coordinates]]
+[[dependency-versions.coordinates]]
 == Managed Dependency Coordinates
 
 The following table provides details of all of the dependency versions that are provided by Spring Boot in its CLI (Command Line Interface), Maven dependency management, and Gradle plugin.
@@ -17,7 +17,7 @@ include::dependency-versions.adoc[]
 
 
 
-[[dependency-versions-properties]]
+[[dependency-versions.properties]]
 == Version Properties
 
 The following table provides all properties that can be used to override the versions managed by Spring Boot.