Author: svn-site-role
Date: Mon May 6 20:55:00 2024
New Revision: 1917538
Log:
Site checkin for project Apache Maven Site
Modified:
maven/website/content/general.html
maven/website/content/guides/mini/guide-reproducible-builds.html
maven/website/content/guides/mini/guide-site.html
maven/website/content/maven-site-1.0-site.jar
Modified: maven/website/content/general.html
==============================================================================
--- maven/website/content/general.html (original)
+++ maven/website/content/general.html Mon May 6 20:55:00 2024
@@ -277,7 +277,7 @@
<p>
Or if a parent pom overrides for compiler plugin default values and
you can't fix it,
- you'll have to explicitely force the values in the compiler plugin
configuration:
+ you'll have to explicitly force the values in the compiler plugin
configuration:
</p>
<div class="verbatim source"><pre class="prettyprint linenums"><project>
@@ -432,7 +432,7 @@ Where: <path-to-file> the path to
</properties>
...
</project></pre></div>
- or if default encoding is overridden in a parent pom that you can't
change, configure the site plugin explicitely:
+ or if default encoding is overridden in a parent pom that you can't
change, configure the site plugin explicitly:
<div class="verbatim source"><pre class="prettyprint linenums"><project>
...
Modified: maven/website/content/guides/mini/guide-reproducible-builds.html
==============================================================================
--- maven/website/content/guides/mini/guide-reproducible-builds.html (original)
+++ maven/website/content/guides/mini/guide-reproducible-builds.html Mon May 6
20:55:00 2024
@@ -207,7 +207,7 @@
<ul>
<li>if you use <a
href="/plugins/maven-release-plugin/">maven-release-plugin</a>, you'll need
<b>version 3.0.0-M1 or later</b>: it will automatically update the timestamp
value in <code>pom.xml</code> during the release in the same commit that
updates version,</li>
<li>if you have a custom release process tooling, you'll need to add the
feature to your release tooling. Notice that if you're using
<code>versions-maven-plugin</code> in custom release scripts, starting with
release 2.9.0, <a class="externalLink"
href="https://github.com/mojohaus/versions-maven-plugin/issues/453";><code>versions:set</code>
goal updates the property</a>.</li>
-<li>instead of explicitely writing a timestamp in their <code>pom.xml</code>,
some people tend to prefer using last Git commit timestamp, like
<code>${git.commit.time}</code> from <a class="externalLink"
href="https://github.com/git-commit-id/git-commit-id-maven-plugin";>git-commit-id-maven-plugin</a>
(with <code><dateFormatTimeZone>UTC</dateFormatTimeZone></code> to
be independent from user's timezone).</li></ul></li></ul>
+<li>instead of explicitly writing a timestamp in their <code>pom.xml</code>,
some people tend to prefer using last Git commit timestamp, like
<code>${git.commit.time}</code> from <a class="externalLink"
href="https://github.com/git-commit-id/git-commit-id-maven-plugin";>git-commit-id-maven-plugin</a>
(with <code><dateFormatTimeZone>UTC</dateFormatTimeZone></code> to
be independent from user's timezone).</li></ul></li></ul>
<p>Don't hesitate to share your questions or solutions on <a
href="/mailing-lists.html">user mailing-list</a>.</p>
<ul>
<li>Q. Which additional plugins need to be updated for Reproducible Builds?
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 Mon May 6 20:55:00 2024
@@ -301,7 +301,7 @@
...
</project></pre></div>
<p>If you have included the appropriate <code><menu
ref="reports"/></code> tag in your <code>site.xml</code>
descriptor, then when you regenerate the site those items will appear in the
menu.</p>
-<p>Many other plugins provide reporting goals: look for "R"
(Reporting) value in the "Type" 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>Many other plugins provide reporting goals: look for "R"
(Reporting) value in the "Type" column of the <a href="/plugins/">
list of plugins</a>. When plugins are both Build and Reporting plugins,
defining explicitly 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>
<h2>Internationalization</h2>
<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>
Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
