<build>
+ <plugins>
+ <plugin>
+ <groupId>org.codehaus.mojo</groupId>
+ <artifactId>flatten-maven-plugin</artifactId>
+ </plugin>
+ </plugins>
+</build>
+diff --git a/reference/html/README.html b/reference/html/README.html index 70928807..13ff0efc 100644 --- a/reference/html/README.html +++ b/reference/html/README.html @@ -105,6 +105,7 @@ $(addBlockSwitches);
Scan Scope to All sources since we
To avoid propagating build setup that is required to build a Spring Cloud project, we’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.
+In order to add it, add the org.codehaus.mojo:flatten-maven-plugin to your pom.xml.
<build>
+ <plugins>
+ <plugin>
+ <groupId>org.codehaus.mojo</groupId>
+ <artifactId>flatten-maven-plugin</artifactId>
+ </plugin>
+ </plugins>
+</build>
+Scan Scope to All sources since we
To avoid propagating build setup that is required to build a Spring Cloud project, we’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.
+In order to add it, add the org.codehaus.mojo:flatten-maven-plugin to your pom.xml.
<build>
+ <plugins>
+ <plugin>
+ <groupId>org.codehaus.mojo</groupId>
+ <artifactId>flatten-maven-plugin</artifactId>
+ </plugin>
+ </plugins>
+</build>
+Scan Scope to All sources since we
To avoid propagating build setup that is required to build a Spring Cloud project, we’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.
+In order to add it, add the org.codehaus.mojo:flatten-maven-plugin to your pom.xml.
<build>
+ <plugins>
+ <plugin>
+ <groupId>org.codehaus.mojo</groupId>
+ <artifactId>flatten-maven-plugin</artifactId>
+ </plugin>
+ </plugins>
+</build>
+