diff --git a/README.adoc b/README.adoc index 53e14d9d..82b9ce6a 100644 --- a/README.adoc +++ b/README.adoc @@ -323,50 +323,48 @@ approach of generating documentation just add these plugins to your `docs` modul docs + + + src/main/antora/resources/antora-resources + true + + pl.project13.maven - git-commit-id-plugin <1> + git-commit-id-plugin org.apache.maven.plugins - maven-dependency-plugin <2> - - - org.apache.maven.plugins - maven-resources-plugin <3> + maven-dependency-plugin org.codehaus.mojo - exec-maven-plugin <4> + exec-maven-plugin - org.asciidoctor - asciidoctor-maven-plugin <5> + io.spring.maven.antora + antora-component-version-maven-plugin + + + io.spring.maven.antora + antora-maven-plugin org.apache.maven.plugins - maven-antrun-plugin <6> + maven-antrun-plugin - maven-deploy-plugin <7> + maven-deploy-plugin - ---- -<1> This plugin downloads sets up all the git information of the project -<2> This plugin downloads the resources of the `spring-cloud-build-docs` module -<3> This plugin unpacks the resources of the `spring-cloud-build-docs` module -<4> This plugin generates an `adoc` file with all the configuration properties from the classpath -<5> This plugin is required to parse the Asciidoctor documentation -<6> This plugin is required to copy resources into proper final destinations and to generate main README.adoc and to assert that no files use unresolved links -<7> This plugin ensures that the generated zip docs will get published IMPORTANT: 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. 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. `spring.sleuth.*`).