Use convention based code imports

Closes gh-29647

Author: philwebb

spring-boot-project/spring-boot-docs/src/docs/asciidoc/actuator/cloud-foundry.adoc

@@ -47,7 +47,4 @@ If you expect the Cloud Foundry endpoints to always be available at `/cloudfound
 The configuration differs, depending on the web server in use.
 For Tomcat, you can add the following configuration:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/actuator/cloudfoundry/customcontextpath/MyCloudFoundryConfiguration.java[]
-----
+include::code:MyCloudFoundryConfiguration[]

spring-boot-project/spring-boot-docs/src/docs/asciidoc/actuator/endpoints.adoc

@@ -328,10 +328,7 @@ If you wish to configure custom security for HTTP endpoints (for example, to all
 
 A typical Spring Security configuration might look something like the following example:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/actuator/endpoints/security/typical/MySecurityConfiguration.java[]
-----
+include::code:typical/MySecurityConfiguration[]
 
 The preceding example uses `EndpointRequest.toAnyEndpoint()` to match a request to any endpoint and then ensures that all have the `ENDPOINT_ADMIN` role.
 Several other matcher methods are also available on `EndpointRequest`.
@@ -351,10 +348,7 @@ You can do so by changing the configprop:management.endpoints.web.exposure.inclu
 
 Additionally, if Spring Security is present, you would need to add custom security configuration that allows unauthenticated access to the endpoints, as the following example shows:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/actuator/endpoints/security/exposeall/MySecurityConfiguration.java[]
-----
+include::code:exposeall/MySecurityConfiguration[]
 
 NOTE: In both of the preceding examples, the configuration applies only to the actuator endpoints.
 Since Spring Boot's security configuration backs off completely in the presence of any `SecurityFilterChain` bean, you need to configure an additional `SecurityFilterChain` bean with rules that apply to the rest of the application.
@@ -443,10 +437,7 @@ If both Jersey and Spring MVC are available, Spring MVC is used.
 
 The following example exposes a read operation that returns a custom object:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/actuator/endpoints/implementingcustom/MyEndpoint.java[tag=read]
-----
+include::code:MyEndpoint[tag=read]
 
 You can also write technology-specific endpoints by using `@JmxEndpoint` or `@WebEndpoint`.
 These endpoints are restricted to their respective technologies.
@@ -480,10 +471,7 @@ Consider the following JSON request body:
 
 You can use this to invoke a write operation that takes `String name` and `int counter` parameters, as the following example shows:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/actuator/endpoints/implementingcustom/input/../MyEndpoint.java[tag=write]
-----
+include::code:../MyEndpoint[tag=write]
 
 TIP: Because endpoints are technology agnostic, only simple types can be specified in the method signature.
 In particular, declaring a single parameter with a `CustomData` type that defines a `name` and `counter` properties is not supported.
@@ -759,10 +747,7 @@ You need to provide an implementation of the `health()` method and return a `Hea
 The `Health` response should include a status and can optionally include additional details to be displayed.
 The following code shows a sample `HealthIndicator` implementation:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/actuator/endpoints/health/writingcustomhealthindicators/MyHealthIndicator.java[]
-----
+include::code:MyHealthIndicator[]
 
 NOTE: The identifier for a given `HealthIndicator` is the name of the bean without the `HealthIndicator` suffix, if it exists.
 In the preceding example, the health information is available in an entry named `my`.
@@ -837,10 +822,7 @@ If you need to register a regular `HealthContributor`, you should wrap it with `
 To provide custom health information from a reactive API, you can register Spring beans that implement the {spring-boot-actuator-module-code}/health/ReactiveHealthIndicator.java[`ReactiveHealthIndicator`] interface.
 The following code shows a sample `ReactiveHealthIndicator` implementation:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/actuator/endpoints/health/reactivehealthindicators/MyReactiveHealthIndicator.java[]
-----
+include::code:MyReactiveHealthIndicator[]
 
 TIP: To handle the error automatically, consider extending from `AbstractReactiveHealthIndicator`.
 
@@ -1283,10 +1265,7 @@ To provide custom application information, you can register Spring beans that im
 
 The following example contributes an `example` entry with a single value:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/actuator/endpoints/info/writingcustominfocontributors/MyInfoContributor.java[]
-----
+include::code:MyInfoContributor[]
 
 If you reach the `info` endpoint, you should see a response that contains the following additional entry:
 

spring-boot-project/spring-boot-docs/src/docs/asciidoc/actuator/metrics.adoc

@@ -65,17 +65,11 @@ Spring Boot also adds any auto-configured registries to the global static compos
 
 You can register any number of `MeterRegistryCustomizer` beans to further configure the registry, such as applying common tags, before any meters are registered with the registry:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/actuator/metrics/gettingstarted/commontags/MyMeterRegistryConfiguration.java[]
-----
+include::code:commontags/MyMeterRegistryConfiguration[]
 
 You can apply customizations to particular registry implementations by being more specific about the generic type:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/actuator/metrics/gettingstarted/specifictype/MyMeterRegistryConfiguration.java[]
-----
+include::code:specifictype/MyMeterRegistryConfiguration[]
 
 Spring Boot also <<actuator#actuator.metrics.supported,configures built-in instrumentation>> that you can control through configuration or dedicated annotation markers.
 
@@ -308,10 +302,7 @@ Micrometer provides a default `HierarchicalNameMapper` that governs how a dimens
 To take control over this behavior, define your `GraphiteMeterRegistry` and supply your own `HierarchicalNameMapper`.
 An auto-configured `GraphiteConfig` and `Clock` beans are provided unless you define your own:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/actuator/metrics/export/graphite/MyGraphiteConfiguration.java[]
-----
+include::code:MyGraphiteConfiguration[]
 ====
 
 
@@ -384,10 +375,7 @@ Micrometer provides a default `HierarchicalNameMapper` that governs how a dimens
 To take control over this behavior, define your `JmxMeterRegistry` and supply your own `HierarchicalNameMapper`.
 An auto-configured `JmxConfig` and `Clock` beans are provided unless you define your own:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/actuator/metrics/export/jmx/MyJmxConfiguration.java[]
-----
+include::code:MyJmxConfiguration[]
 ====
 
 
@@ -1045,10 +1033,7 @@ Each metric is tagged with the following information by default:
 
 To replace the default metric tags, define a `MongoCommandTagsProvider` bean, as the following example shows:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/actuator/metrics/supported/mongodb/command/MyCommandTagsProviderConfiguration.java[]
-----
+include::code:MyCommandTagsProviderConfiguration[]
 
 To disable the auto-configured command metrics, set the following property:
 
@@ -1086,10 +1071,7 @@ Each metric is tagged with the following information by default:
 
 To replace the default metric tags, define a `MongoConnectionPoolTagsProvider` bean:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/actuator/metrics/supported/mongodb/connectionpool/MyConnectionPoolTagsProviderConfiguration.java[]
-----
+include::code:MyConnectionPoolTagsProviderConfiguration[]
 
 To disable the auto-configured connection pool metrics, set the following property:
 
@@ -1118,24 +1100,15 @@ If supported, you can use the annotation at either the class level or the method
 
 For example, the following code shows how you can use the annotation to instrument all request mappings in a `@RestController`:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/actuator/metrics/supported/timedannotation/all/MyController.java[]
-----
+include::code:all/MyController[]
 
 If you want only to instrument a single mapping, you can use the annotation on the method instead of the class:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/actuator/metrics/supported/timedannotation/single/MyController.java[]
-----
+include::code:single/MyController[]
 
 You can also combine class-level and method-level annotations if you want to change the timing details for a specific method:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/actuator/metrics/supported/timedannotation/change/MyController.java[]
-----
+include::code:change/MyController[]
 
 NOTE: A `@Timed` annotation with `longTask = true` enables a long task timer for the method.
 Long task timers require a separate metric name and can be stacked with a short task timer.
@@ -1153,17 +1126,11 @@ For more detail, see the {lettuce-docs}#command.latency.metrics.micrometer[Micro
 === Registering Custom Metrics
 To register custom metrics, inject `MeterRegistry` into your component:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/actuator/metrics/registeringcustom/MyBean.java[]
-----
+include::code:MyBean[]
 
 If your metrics depend on other beans, we recommend that you use a `MeterBinder` to register them:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/actuator/metrics/registeringcustom/MyMeterBinderConfiguration.java[]
-----
+include::code:MyMeterBinderConfiguration[]
 
 Using a `MeterBinder` ensures that the correct dependency relationships are set up and that the bean is available when the metric's value is retrieved.
 A `MeterBinder` implementation can also be useful if you find that you repeatedly instrument a suite of metrics across components or applications.
@@ -1178,10 +1145,7 @@ If you need to apply customizations to specific `Meter` instances, you can use t
 
 For example, if you want to rename the `mytag.region` tag to `mytag.area` for all meter IDs beginning with `com.example`, you can do the following:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/actuator/metrics/customizing/MyMetricsFilterConfiguration.java[]
-----
+include::code:MyMetricsFilterConfiguration[]
 
 NOTE: By default, all `MeterFilter` beans are automatically bound to the Spring-managed `MeterRegistry`.
 Make sure to register your metrics by using the Spring-managed `MeterRegistry` and not any of the static methods on `Metrics`.

spring-boot-project/spring-boot-docs/src/docs/asciidoc/attributes.adoc

@@ -18,8 +18,8 @@
 :github-raw: https://raw.githubusercontent.com/{github-repo}/{github-tag}
 :github-issues: https://github.com/{github-repo}/issues/
 :github-wiki: https://github.com/{github-repo}/wiki
-:docs-java: ../../main/java/org/springframework/boot/docs
-:docs-groovy: ../../main/groovy/org/springframework/boot/docs
+:docs-java: {docdir}/../main/java/org/springframework/boot/docs
+:docs-groovy: {docdir}/../main/groovy/org/springframework/boot/docs
 :docs-resources: ../../main/resources
 :spring-boot-code: https://github.com/{github-repo}/tree/{github-tag}
 :spring-boot-api: https://docs.spring.io/spring-boot/docs/{spring-boot-version}/api

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

@@ -37,7 +37,4 @@ An exception is thrown if more than one candidate is found.
 === Example Repackage Implementation
 The following example shows a typical repackage implementation:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/buildtoolplugins/otherbuildsystems/examplerepackageimplementation/MyBuildTool.java[]
-----
+include::code:MyBuildTool[]

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

@@ -69,10 +69,7 @@ The annotation processor also supports the use of the `@Data`, `@Value`, `@Gette
 
 Consider the following example:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/configurationmetadata/annotationprocessor/automaticmetadatageneration/MyServerProperties.java[]
-----
+include::code:MyServerProperties[]
 
 This exposes three properties where `my.server.name` has no default and `my.server.ip` and `my.server.port` defaults to `"127.0.0.1"` and `9797` respectively.
 The Javadoc on fields is used to populate the `description` attribute. For instance, the description of `my.server.ip` is "IP address to listen to.".
@@ -86,10 +83,7 @@ Also, the annotation processor cannot auto-detect default values for ``Enum``s a
 For cases where the default value could not be detected, <<configuration-metadata#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[]
-----
+include::code:MyMessagingProperties[]
 
 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>>:
 
@@ -117,10 +111,7 @@ The annotation processor automatically considers inner classes as nested propert
 Rather than documenting the `ip` and `port` at the root of the namespace, we could create a sub-namespace for it.
 Consider the updated example:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/configurationmetadata/annotationprocessor/automaticmetadatageneration/nestedproperties/MyServerProperties.java[]
-----
+include::code:MyServerProperties[]
 
 The preceding example produces metadata information for `my.server.name`, `my.server.host.ip`, and `my.server.host.port` properties.
 You can use the `@NestedConfigurationProperty` annotation on a field to indicate that a regular (non-inner) class should be treated as if it were nested.

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

@@ -208,10 +208,7 @@ Deprecation can also be specified declaratively in code by adding the `@Deprecat
 For instance, assume that the `my.app.target` property was confusing and was renamed to `my.app.name`.
 The following example shows how to handle that situation:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/configurationmetadata/format/property/MyProperties.java[]
-----
+include::code:MyProperties[]
 
 NOTE: There is no way to set a `level`.
 `warning` is always assumed, since code is still handling the property.

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

@@ -18,10 +18,7 @@ The special `.keys` and `.values` suffixes must refer to the keys and the values
 
 Assume a `my.contexts` maps magic `String` values to an integer, as shown in the following example:
 
-[source,java,indent=0,subs="verbatim"]
-----
-include::{docs-java}/configurationmetadata/manualhints/valuehint/MyProperties.java[]
-----
+include::code:MyProperties[]
 
 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#configuration-metadata.annotation-processor.adding-additional-metadata,the manual metadata of the module>>:

spring-boot-project/spring-boot-docs/src/docs/asciidoc/data.adoc

@@ -8,4 +8,4 @@ include::data/sql.adoc[]
 
 include::data/nosql.adoc[]
 
-include::data/whats-next.adoc[]
+include::data/whats-next.adoc[]