svn commit: r1897801 - in /maven/website/content: apache-maven.pdf guides/mini/guide-site.html maven-site-1.0-site.jar

[sv...@apache.org]

Author: svn-site-role
Date: Sun Feb  6 09:21:38 2022
New Revision: 1897801

Log:
Site checkin for project Apache Maven Site

Modified:
    maven/website/content/apache-maven.pdf
    maven/website/content/guides/mini/guide-site.html
    maven/website/content/maven-site-1.0-site.jar

Modified: maven/website/content/apache-maven.pdf
==============================================================================
Binary files - no diff available.

Modified: maven/website/content/guides/mini/guide-site.html
==============================================================================
--- maven/website/content/guides/mini/guide-site.html (original)
+++ maven/website/content/guides/mini/guide-site.html Sun Feb  6 09:21:38 2022
@@ -281,7 +281,7 @@ Jason van Zyl" />
 <li>Project Team</li>
 <li>License</li></ul>
 <p>To find out more please refer to the <a href="../../plugins/maven-project-info-reports-plugin/">Project Info Reports Plugin</a>.</p>
-<p>To add these reports to your site, you must add the plugins to a special <code>&lt;reporting&gt;</code> section in the POM. The following example shows how to configure the standard project information reports that display information from the POM in a friendly format:</p>
+<p>To add these reports to your site, you must add the Project Info Reports plugin to a special <code>&lt;reporting&gt;</code> section in the POM. The following example shows how to configure the standard project information reports that display information from the POM in a friendly format:</p>
 <div class="source"><pre class="prettyprint linenums">&lt;project&gt;
   ...
   &lt;reporting&gt;
@@ -289,14 +289,15 @@ Jason van Zyl" />
       &lt;plugin&gt;
         &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
         &lt;artifactId&gt;maven-project-info-reports-plugin&lt;/artifactId&gt;
-        &lt;version&gt;2.8&lt;/version&gt;
+        &lt;version&gt;2.8&lt;/version&gt;&lt;!-- define version here if not already defined in build/plugins or build/pluginManagement --&gt;
       &lt;/plugin&gt;
     &lt;/plugins&gt;
   &lt;/reporting&gt;
   ...
 &lt;/project&gt;</pre></div>
 <p>If you have included the appropriate <code>&lt;menu ref=&quot;reports&quot;/&gt;</code> tag in your <code>site.xml</code> descriptor, then when you regenerate the site those items will appear in the menu.</p>
-<p><b>Note:</b> Many report plugins provide a parameter called <code>outputDirectory</code> or similar to specify the destination for their report outputs. This parameter is only relevant if the report plugin is run standalone, i.e. by invocation directly from the command line. In constrast, when reports are generated as part of the site, the configuration of the Maven Site Plugin will determine the effective output directory to ensure that all reports end up in a central location.</p></section><section>
+<p>Many other plugins provide reporting goals: look for &quot;R&quot; (Reporting) value in the &quot;Type&quot; column of the <a href="/plugins/"> list of plugins</a>. When plugins are both Build and Reporting plugins, defining explicitely the version in the reporting section is usually not necessary since reporting will use the version from <code>build/plugins</code> or <code>build/pluginManagement</code>. Since Maven Site Plugin 3.4, reporting plugin also get configuration from <code>build/pluginManagement</code>.</p>
+<p><b>Note:</b> Many report plugins provide a parameter called <code>outputDirectory</code> or similar to specify the destination for their report outputs. This parameter is only relevant if the report plugin is run standalone, i.e. by invocation directly from the command line. In contrast, when reports are generated as part of the site, the configuration of the Maven Site Plugin will determine the effective output directory to ensure that all reports end up in a central location.</p></section><section>
 <h3><a name="Internationalization"></a>Internationalization</h3>
 <p>Internationalization in Maven is very simple, as long as the reports you are using have that particular locale defined. For an overview of supported languages and instructions on how to add further languages, please see the related article <a href="../../plugins/maven-site-plugin/i18n.html"> Internationalization</a> from the Maven Site Plugin.</p>
 <p>To enable multiple locales, add a configuration similar to the following to your POM:</p>

Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.