diff --git a/reference/html/README.html b/reference/html/README.html index e4a3cbdd..d986e273 100644 --- a/reference/html/README.html +++ b/reference/html/README.html @@ -563,7 +563,7 @@ The order of plugin declaration is important!
-

In order for the build to generate the adoc file with all your configuration properties, your docs module should contain all the dependencies on the classpath, that you would want to scan for configuration properties. The file will be output to ${docsModule}/src/main/asciidoc/configprops.adoc file (configurable via the configprops.path property).

+

In order for the build to generate the adoc file with all your configuration properties, your docs module should contain all the dependencies on the classpath, that you would want to scan for configuration properties. The file will be output to ${docsModule}/src/main/asciidoc/_configprops.adoc file (configurable via the configprops.path property).

If you want to modify which of the configuration properties are put in the table, you can tweak the configprops.inclusionPattern pattern to include only a subset of the properties (e.g. <configprops.inclusionPattern>spring.sleuth.*</configprops.inclusionPattern>).

diff --git a/reference/html/index.html b/reference/html/index.html index 2a834663..abaed6f2 100644 --- a/reference/html/index.html +++ b/reference/html/index.html @@ -564,7 +564,7 @@ The order of plugin declaration is important!
-

In order for the build to generate the adoc file with all your configuration properties, your docs module should contain all the dependencies on the classpath, that you would want to scan for configuration properties. The file will be output to ${docsModule}/src/main/asciidoc/configprops.adoc file (configurable via the configprops.path property).

+

In order for the build to generate the adoc file with all your configuration properties, your docs module should contain all the dependencies on the classpath, that you would want to scan for configuration properties. The file will be output to ${docsModule}/src/main/asciidoc/_configprops.adoc file (configurable via the configprops.path property).

If you want to modify which of the configuration properties are put in the table, you can tweak the configprops.inclusionPattern pattern to include only a subset of the properties (e.g. <configprops.inclusionPattern>spring.sleuth.*</configprops.inclusionPattern>).

diff --git a/reference/html/spring-cloud-build.html b/reference/html/spring-cloud-build.html index 2a834663..abaed6f2 100644 --- a/reference/html/spring-cloud-build.html +++ b/reference/html/spring-cloud-build.html @@ -564,7 +564,7 @@ The order of plugin declaration is important!
-

In order for the build to generate the adoc file with all your configuration properties, your docs module should contain all the dependencies on the classpath, that you would want to scan for configuration properties. The file will be output to ${docsModule}/src/main/asciidoc/configprops.adoc file (configurable via the configprops.path property).

+

In order for the build to generate the adoc file with all your configuration properties, your docs module should contain all the dependencies on the classpath, that you would want to scan for configuration properties. The file will be output to ${docsModule}/src/main/asciidoc/_configprops.adoc file (configurable via the configprops.path property).

If you want to modify which of the configuration properties are put in the table, you can tweak the configprops.inclusionPattern pattern to include only a subset of the properties (e.g. <configprops.inclusionPattern>spring.sleuth.*</configprops.inclusionPattern>).