Sync docs from master to gh-pages

This commit is contained in:
buildmaster
2019-11-07 13:16:00 +00:00
parent ae1821eeb3
commit 02598bcabf
4 changed files with 160 additions and 0 deletions

View File

@@ -105,6 +105,7 @@ $(addBlockSwitches);
<li><a href="#_ide_setup">IDE setup</a></li>
</ul>
</li>
<li><a href="#_flattening_the_poms">Flattening the POMs</a></li>
<li><a href="#_reusing_the_documentation">Reusing the documentation</a></li>
<li><a href="#_updating_the_guides">Updating the guides</a></li>
</ul>
@@ -477,6 +478,29 @@ Remember to set the <code>Scan Scope</code> to <code>All sources</code> since we
</div>
</div>
<div class="sect1">
<h2 id="_flattening_the_poms"><a class="link" href="#_flattening_the_poms">Flattening the POMs</a></h2>
<div class="sectionbody">
<div class="paragraph">
<p>To avoid propagating build setup that is required to build a Spring Cloud project, we&#8217;re using the maven flatten plugin. It has the advantage of letting you use whatever features you need while publishing "clean" pom to the repository.</p>
</div>
<div class="paragraph">
<p>In order to add it, add the <code>org.codehaus.mojo:flatten-maven-plugin</code> to your <code>pom.xml</code>.</p>
</div>
<div class="listingblock">
<div class="content">
<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;build&gt;
&lt;plugins&gt;
&lt;plugin&gt;
&lt;groupId&gt;org.codehaus.mojo&lt;/groupId&gt;
&lt;artifactId&gt;flatten-maven-plugin&lt;/artifactId&gt;
&lt;/plugin&gt;
&lt;/plugins&gt;
&lt;/build&gt;</code></pre>
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_reusing_the_documentation"><a class="link" href="#_reusing_the_documentation">Reusing the documentation</a></h2>
<div class="sectionbody">
<div class="paragraph">

View File

@@ -106,6 +106,7 @@ $(addBlockSwitches);
<li><a href="#_ide_setup">IDE setup</a></li>
</ul>
</li>
<li><a href="#_flattening_the_poms">Flattening the POMs</a></li>
<li><a href="#_reusing_the_documentation">Reusing the documentation</a></li>
<li><a href="#_updating_the_guides">Updating the guides</a></li>
</ul>
@@ -478,6 +479,29 @@ Remember to set the <code>Scan Scope</code> to <code>All sources</code> since we
</div>
</div>
<div class="sect1">
<h2 id="_flattening_the_poms"><a class="link" href="#_flattening_the_poms">Flattening the POMs</a></h2>
<div class="sectionbody">
<div class="paragraph">
<p>To avoid propagating build setup that is required to build a Spring Cloud project, we&#8217;re using the maven flatten plugin. It has the advantage of letting you use whatever features you need while publishing "clean" pom to the repository.</p>
</div>
<div class="paragraph">
<p>In order to add it, add the <code>org.codehaus.mojo:flatten-maven-plugin</code> to your <code>pom.xml</code>.</p>
</div>
<div class="listingblock">
<div class="content">
<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;build&gt;
&lt;plugins&gt;
&lt;plugin&gt;
&lt;groupId&gt;org.codehaus.mojo&lt;/groupId&gt;
&lt;artifactId&gt;flatten-maven-plugin&lt;/artifactId&gt;
&lt;/plugin&gt;
&lt;/plugins&gt;
&lt;/build&gt;</code></pre>
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_reusing_the_documentation"><a class="link" href="#_reusing_the_documentation">Reusing the documentation</a></h2>
<div class="sectionbody">
<div class="paragraph">

View File

@@ -106,6 +106,7 @@ $(addBlockSwitches);
<li><a href="#_ide_setup">IDE setup</a></li>
</ul>
</li>
<li><a href="#_flattening_the_poms">Flattening the POMs</a></li>
<li><a href="#_reusing_the_documentation">Reusing the documentation</a></li>
<li><a href="#_updating_the_guides">Updating the guides</a></li>
</ul>
@@ -478,6 +479,29 @@ Remember to set the <code>Scan Scope</code> to <code>All sources</code> since we
</div>
</div>
<div class="sect1">
<h2 id="_flattening_the_poms"><a class="link" href="#_flattening_the_poms">Flattening the POMs</a></h2>
<div class="sectionbody">
<div class="paragraph">
<p>To avoid propagating build setup that is required to build a Spring Cloud project, we&#8217;re using the maven flatten plugin. It has the advantage of letting you use whatever features you need while publishing "clean" pom to the repository.</p>
</div>
<div class="paragraph">
<p>In order to add it, add the <code>org.codehaus.mojo:flatten-maven-plugin</code> to your <code>pom.xml</code>.</p>
</div>
<div class="listingblock">
<div class="content">
<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;build&gt;
&lt;plugins&gt;
&lt;plugin&gt;
&lt;groupId&gt;org.codehaus.mojo&lt;/groupId&gt;
&lt;artifactId&gt;flatten-maven-plugin&lt;/artifactId&gt;
&lt;/plugin&gt;
&lt;/plugins&gt;
&lt;/build&gt;</code></pre>
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_reusing_the_documentation"><a class="link" href="#_reusing_the_documentation">Reusing the documentation</a></h2>
<div class="sectionbody">
<div class="paragraph">