Sync docs from master to gh-pages
This commit is contained in:
@@ -563,7 +563,7 @@ The order of plugin declaration is important!
|
||||
</table>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>In order for the build to generate the <code>adoc</code> file with all your configuration properties, your <code>docs</code> module should contain all the dependencies on the classpath, that you would want to scan for configuration properties. The file will be output to <code>${docsModule}/src/main/asciidoc/configprops.adoc</code> file (configurable via the <code>configprops.path</code> property).</p>
|
||||
<p>In order for the build to generate the <code>adoc</code> file with all your configuration properties, your <code>docs</code> module should contain all the dependencies on the classpath, that you would want to scan for configuration properties. The file will be output to <code>${docsModule}/src/main/asciidoc/_configprops.adoc</code> file (configurable via the <code>configprops.path</code> property).</p>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>If you want to modify which of the configuration properties are put in the table, you can tweak the <code>configprops.inclusionPattern</code> pattern to include only a subset of the properties (e.g. <code><configprops.inclusionPattern>spring.sleuth.*</configprops.inclusionPattern></code>).</p>
|
||||
|
||||
@@ -564,7 +564,7 @@ The order of plugin declaration is important!
|
||||
</table>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>In order for the build to generate the <code>adoc</code> file with all your configuration properties, your <code>docs</code> module should contain all the dependencies on the classpath, that you would want to scan for configuration properties. The file will be output to <code>${docsModule}/src/main/asciidoc/configprops.adoc</code> file (configurable via the <code>configprops.path</code> property).</p>
|
||||
<p>In order for the build to generate the <code>adoc</code> file with all your configuration properties, your <code>docs</code> module should contain all the dependencies on the classpath, that you would want to scan for configuration properties. The file will be output to <code>${docsModule}/src/main/asciidoc/_configprops.adoc</code> file (configurable via the <code>configprops.path</code> property).</p>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>If you want to modify which of the configuration properties are put in the table, you can tweak the <code>configprops.inclusionPattern</code> pattern to include only a subset of the properties (e.g. <code><configprops.inclusionPattern>spring.sleuth.*</configprops.inclusionPattern></code>).</p>
|
||||
|
||||
@@ -564,7 +564,7 @@ The order of plugin declaration is important!
|
||||
</table>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>In order for the build to generate the <code>adoc</code> file with all your configuration properties, your <code>docs</code> module should contain all the dependencies on the classpath, that you would want to scan for configuration properties. The file will be output to <code>${docsModule}/src/main/asciidoc/configprops.adoc</code> file (configurable via the <code>configprops.path</code> property).</p>
|
||||
<p>In order for the build to generate the <code>adoc</code> file with all your configuration properties, your <code>docs</code> module should contain all the dependencies on the classpath, that you would want to scan for configuration properties. The file will be output to <code>${docsModule}/src/main/asciidoc/_configprops.adoc</code> file (configurable via the <code>configprops.path</code> property).</p>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>If you want to modify which of the configuration properties are put in the table, you can tweak the <code>configprops.inclusionPattern</code> pattern to include only a subset of the properties (e.g. <code><configprops.inclusionPattern>spring.sleuth.*</configprops.inclusionPattern></code>).</p>
|
||||
|
||||
Reference in New Issue
Block a user