rename IT. merge docs

maven-plugin-report-plugin/src/site/apt/examples/generate-report.apt.vm

@@ -45,6 +45,45 @@ Configuring Generation of Documentation Reports
   </reporting>
   ...
 </project>
++-----+
+
+Generate Plugin Report without duplicate execution of phase process-classes.
+
+ * The standard goal <<<report>>> invokes separate lifecyle of <<<process-classes>>>.
+
+ * In a CI environment you now might execute something like <<<mvn clean deploy site-deploy>>>.
+
+ * During <<<site>>> build the standard reports will trigger <<<process-classes>>> again, depending on your build this may take some time, because
+ stuff like <<<enforcer>>> or generating stubs from a WDSL will be invoked again, which may lead
+ to longer build times.
+
+ * See {{{https://issues.apache.org/jira/browse/MPLUGIN-529}MPLUGIN-529}} as well.
+
+ * As of version 3.14.0 a new report is defined, <<<report-no-fork>>> which will not trigger above phase a second time.
+
+ * Configure this in your <<<reporting>>> section as follows:
+
++-----+
+<project>
+  ...
+  <reporting>
+    <plugins>
+      <plugin>
+        <groupId>org.apache.maven.plugins</groupId>
+        <artifactId>maven-plugin-report-plugin</artifactId>
+        <version>${project.version}</version>
+        <reportSets>
+          <reportSet>
+            <reports>
+              <report>report-no-fork</report>
+            </reports>
+          </reportSet>
+        </reportSets>
+      </plugin>
+    </plugins>
+  </reporting>
+  ...
+</project>
 +-----+
 
  The documentation is generated by default in <<<$\{project.build.directory\}/site>>>.

maven-plugin-report-plugin/src/site/apt/index.apt

@@ -59,5 +59,3 @@ Maven Plugin Report Plugin
    The following examples shows how to use the Plugin Report Plugin in more advanced usecases:
 
    * {{{./examples/generate-report.html}Configuring Generation of Documentation Reports}}
-
-   * {{{./examples/nofork.html}Generate Plugin Report without duplicate execution of phase process-classes}}