Move appendix subsections under appendix section

This involved a small code change to the generated configuration properties snippets: the section id has to start with 'appendix.', otherwise the section-id asciidoctor extension complains.

See gh-27003.

Author: mhalbritter

buildSrc/src/main/java/org/springframework/boot/build/context/properties/Snippets.java

@@ -90,7 +90,8 @@ private Set<String> writeSnippet(Path outputDirectory, Snippet snippet, Set<Stri
 
 	private Asciidoc getAsciidoc(Snippet snippet, Table table) {
 		Asciidoc asciidoc = new Asciidoc();
-		asciidoc.appendln("[[" + snippet.getAnchor() + "]]");
+		// We have to prepend 'appendix.' as a section id here, otherwise the spring-asciidoctor-extensions:section-id asciidoctor extension complains
+		asciidoc.appendln("[[appendix." + snippet.getAnchor() + "]]");
 		asciidoc.appendln("== ", snippet.getTitle());
 		table.write(asciidoc);
 		return asciidoc;

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

@@ -1,5 +1,5 @@
 [appendix]
-[[application-properties]]
+[[appendix.application-properties]]
 = Common Application Properties
 include::attributes.adoc[]
 

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

@@ -1,5 +1,5 @@
 [appendix]
-[[auto-configuration-classes]]
+[[appendix.auto-configuration-classes]]
 = Auto-configuration Classes
 include::attributes.adoc[]
 

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

@@ -1,4 +1,4 @@
-[[auto-configuration-classes.actuator]]
+[[appendix.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/auto-configuration-classes/core.adoc

@@ -1,4 +1,4 @@
-[[auto-configuration-classes.core]]
+[[appendix.auto-configuration-classes.core]]
 == spring-boot-autoconfigure
 The following auto-configuration classes are from the `spring-boot-autoconfigure` module:
 

spring-boot-project/spring-boot-docs/src/docs/asciidoc/build-tool-plugins/other-build-systems.adoc

@@ -1,7 +1,7 @@
 [[build-tool-plugins.other-build-systems]]
 == Supporting Other Build Systems
 If you want to use a build tool other than Maven, Gradle, or Ant, you likely need to develop your own plugin.
-Executable jars need to follow a specific format and certain entries need to be written in an uncompressed form (see the "`<<executable-jar#executable-jar, executable jar format>>`" section in the appendix for details).
+Executable jars need to follow a specific format and certain entries need to be written in an uncompressed form (see the "`<<executable-jar#appendix.executable-jar, executable jar format>>`" section in the appendix for details).
 
 The Spring Boot Maven and Gradle plugins both make use of `spring-boot-loader-tools` to actually generate jars.
 If you need to, you may use this library directly.

spring-boot-project/spring-boot-docs/src/docs/asciidoc/build-tool-plugins/whats-next.adoc

@@ -1,6 +1,6 @@
 [[build-tool-plugins.whats-next]]
 == What to Read Next
 If you are interested in how the build tool plugins work, you can look at the {spring-boot-code}/spring-boot-project/spring-boot-tools[`spring-boot-tools`] module on GitHub.
-More technical details of the executable jar format are covered in <<executable-jar#executable-jar,the appendix>>.
+More technical details of the executable jar format are covered in <<executable-jar#appendix.executable-jar,the appendix>>.
 
 If you have specific build-related questions, you can check out the "`<<howto#howto, how-to>>`" guides.

spring-boot-project/spring-boot-docs/src/docs/asciidoc/cli/using-the-cli.adoc

@@ -146,7 +146,7 @@ Doing so consults Spring Boot's default dependency metadata to deduce the artifa
 
 NOTE: The default metadata is tied to the version of the CLI that you use.
 It changes only when you move to a new version of the CLI, putting you in control of when the versions of your dependencies may change.
-A table showing the dependencies and their versions that are included in the default metadata can be found in the <<dependency-versions#dependency-versions,appendix>>.
+A table showing the dependencies and their versions that are included in the default metadata can be found in the <<dependency-versions#appendix.dependency-versions,appendix>>.
 
 
 

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

@@ -1,5 +1,5 @@
 [appendix]
-[[configuration-metadata]]
+[[appendix.configuration-metadata]]
 = Configuration Metadata
 include::attributes.adoc[]
 
@@ -9,7 +9,7 @@ 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#configuration-metadata.annotation-processor.adding-additional-metadata,write part of the metadata manually>> for corner cases or more advanced use cases.
+However, it is possible to <<configuration-metadata#appendix.configuration-metadata.annotation-processor.adding-additional-metadata,write part of the metadata manually>> for corner cases or more advanced use cases.
 
 
 

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

@@ -1,11 +1,11 @@
-[[configuration-metadata.annotation-processor]]
+[[appendix.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.configuring]]
+[[appendix.configuration-metadata.annotation-processor.configuring]]
 === Configuring the Annotation Processor
 To use the processor, include a dependency on `spring-boot-configuration-processor`.
 
@@ -59,7 +59,7 @@ You could also let the AspectJ plugin run all the processing and disable annotat
 
 
 
-[[configuration-metadata.annotation-processor.automatic-metadata-generation]]
+[[appendix.configuration-metadata.annotation-processor.automatic-metadata-generation]]
 === Automatic Metadata Generation
 The processor picks up both classes and methods that are annotated with `@ConfigurationProperties`.
 
@@ -83,15 +83,15 @@ 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#configuration-metadata.annotation-processor.adding-additional-metadata,manual metadata>> should be provided.
+For cases where the default value could not be detected, <<configuration-metadata#appendix.configuration-metadata.annotation-processor.adding-additional-metadata,manual metadata>> should be provided.
 Consider the following example:
 
 [source,java,indent=0,subs="verbatim"]
 ----
 include::{docs-java}/configurationmetadata/annotationprocessor/automaticmetadatageneration/MyMessagingProperties.java[]
 ----
 
-In order to document default values for properties in the class above, you could add the following content to <<configuration-metadata#configuration-metadata.annotation-processor.adding-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#appendix.configuration-metadata.annotation-processor.adding-additional-metadata,the manual metadata of the module>>:
 
 [source,json,indent=0,subs="verbatim"]
 ----
@@ -111,7 +111,7 @@ NOTE: Only the `name` of the property is required to document additional metadat
 
 
 
-[[configuration-metadata.annotation-processor.automatic-metadata-generation.nested-properties]]
+[[appendix.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.
@@ -129,7 +129,7 @@ TIP: This has no effect on collections and maps, as those types are automaticall
 
 
 
-[[configuration-metadata.annotation-processor.adding-additional-metadata]]
+[[appendix.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.