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">

View File

@@ -0,0 +1,88 @@
<?xml version="1.0" encoding="UTF-8"?>
<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-dependencies</artifactId>
<version>2.2.1.RELEASE</version>
<relativePath></relativePath>
</parent>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-build-dependencies</artifactId>
<version>2.2.0.BUILD-SNAPSHOT</version>
<packaging>pom</packaging>
<name>spring-cloud-build-dependencies</name>
<description>Spring Cloud Build Dependencies: an internal BOM for use with Spring
Cloud projects. Use as a BOM or by inheriting from the spring-cloud build parent.</description>
<url>https://projects.spring.io/spring-boot/#/spring-cloud-build-dependencies</url>
<licenses>
<license>
<name>Apache License, Version 2.0</name>
<url>https://www.apache.org/licenses/LICENSE-2.0</url>
</license>
</licenses>
<developers>
<developer>
<name>Pivotal</name>
<email>info@pivotal.io</email>
<organization>Pivotal Software, Inc.</organization>
<organizationUrl>https://www.spring.io</organizationUrl>
</developer>
</developers>
<scm>
<url>https://github.com/spring-projects/spring-boot/spring-cloud-build-dependencies</url>
</scm>
<distributionManagement>
<repository>
<id>repo.spring.io</id>
<name>Spring Release Repository</name>
<url>https://repo.spring.io/libs-release-local</url>
</repository>
<snapshotRepository>
<id>repo.spring.io</id>
<name>Spring Snapshot Repository</name>
<url>https://repo.spring.io/libs-snapshot-local</url>
</snapshotRepository>
<site>
<id>spring-docs</id>
<url>scp://static.springframework.org/var/www/domains/springframework.org/static/htdocs/spring-cloud/docs/spring-cloud-build-dependencies/2.2.0.BUILD-SNAPSHOT</url>
</site>
<downloadUrl>https://github.com/spring-cloud</downloadUrl>
</distributionManagement>
<properties>
<spring-boot.version>2.2.1.RELEASE</spring-boot.version>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>
<profiles>
<profile>
<id>spring</id>
<repositories>
<repository>
<snapshots>
<enabled>true</enabled>
</snapshots>
<id>spring-snapshots</id>
<name>Spring Snapshots</name>
<url>https://repo.spring.io/libs-snapshot-local</url>
</repository>
<repository>
<snapshots>
<enabled>false</enabled>
</snapshots>
<id>spring-milestones</id>
<name>Spring Milestones</name>
<url>https://repo.spring.io/libs-milestone-local</url>
</repository>
<repository>
<snapshots>
<enabled>false</enabled>
</snapshots>
<id>spring-releases</id>
<name>Spring Releases</name>
<url>https://repo.spring.io/release</url>
</repository>
</repositories>
</profile>
</profiles>
</project>