Modified:
maven/website/content/guides/introduction/introduction-to-profiles.html
==============================================================================
--- maven/website/content/guides/introduction/introduction-to-profiles.html
(original)
+++ maven/website/content/guides/introduction/introduction-to-profiles.html Sat
Feb 18 18:17:30 2023
@@ -176,7 +176,9 @@ under the License.
<li>
<p><a href="#explicit-profile-activation">Explicit profile
activation</a></p></li>
<li>
-<p><a href="#implici-profile-activation">Implicit profile
activation</a></p></li>
+<p><a href="#implici-profile-activation">Implicit profile activation</a></p>
+<ul>
+
<li>
<p><a href="#jdk">JDK</a></p></li>
<li>
@@ -185,6 +187,7 @@ under the License.
<p><a href="#property">Property</a></p></li>
<li>
<p><a href="#files">Files</a></p></li>
+</ul></li>
<li>
<p><a href="#deactivating-a-profile">Deactivating a profile</a></p></li>
<li>
@@ -264,7 +267,7 @@ under the License.
</code></pre></div>
<p>Profiles can be activated in the Maven settings, via the
<code><activeProfiles></code> section. This section takes a list of
<code><activeProfile></code> elements, each containing a profile-id
inside.</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
...
<activeProfiles>
<activeProfile>profile-1</activeProfile>
@@ -277,7 +280,7 @@ under the License.
<p>Profiles can be automatically triggered based on the detected state of the
build environment. These triggers are specified via an
<code><activation></code> section in the profile itself. Currently, this
detection is limited to JDK version matching, operating system matching or the
presence/the value of a system property. Here are some examples.</p>JDK
<p>The following configuration will trigger the profile when the JDK's version
<em>starts with</em> “1.4” (eg. “1.4.0_08”,
“1.4.2_07”, “1.4”), in particular it <em>won't be
active</em> for <strong>newer</strong> versions like “1.8” or
“11”:</p>
-<div class="source"><pre class="prettyprint linenums"><code><profiles>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><profiles>
<profile>
<activation>
<jdk>1.4</jdk>
@@ -288,7 +291,7 @@ under the License.
</code></pre></div>
<p>Ranges can also be used as of Maven 2.1 (refer to the <a
href="/enforcer/enforcer-rules/versionRanges.html">Enforcer Version Range
Syntax</a> for more information). Range values must start with either
<code>\[</code> or <code>(</code> otherwise the value is interpreted as prefix.
The following honours versions 1.3, 1.4 and 1.5.</p>
-<div class="source"><pre class="prettyprint linenums"><code><profiles>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><profiles>
<profile>
<activation>
<jdk>[1.3,1.6)</jdk>
@@ -300,7 +303,7 @@ under the License.
<p><em>Note:</em> an upper bound such as <code>,1.5\]</code> is likely not to
include most releases of 1.5, since they will have an additional
“patch” release such as <code>_05</code> that is not taken into
consideration in the above range.</p>OS
<p>This next one will activate based on the detected operating system. See the
<a href="/enforcer/enforcer-rules/requireOS.html">Maven Enforcer Plugin</a> for
more details about OS values.</p>
-<div class="source"><pre class="prettyprint linenums"><code><profiles>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><profiles>
<profile>
<activation>
<os>
@@ -316,7 +319,7 @@ under the License.
</code></pre></div>Property
<p>The profile below will be activated when the system property
“debug” is specified with any value:</p>
-<div class="source"><pre class="prettyprint linenums"><code><profiles>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><profiles>
<profile>
<activation>
<property>
@@ -329,7 +332,7 @@ under the License.
</code></pre></div>
<p>The following profile will be activated when the system property
“debug” is not defined at all:</p>
-<div class="source"><pre class="prettyprint linenums"><code><profiles>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><profiles>
<profile>
<activation>
<property>
@@ -342,7 +345,7 @@ under the License.
</code></pre></div>
<p>The following profile will be activated when the system property
“debug” is not defined, or is defined with a value which is not
“true”.</p>
-<div class="source"><pre class="prettyprint linenums"><code><profiles>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><profiles>
<profile>
<activation>
<property>
@@ -361,7 +364,7 @@ mvn groupId:artifactId:goal -Ddebug=fals
</code></pre></div>
<p>The next example will trigger the profile when the system property
“environment” is specified with the value
“test”:</p>
-<div class="source"><pre class="prettyprint linenums"><code><profiles>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><profiles>
<profile>
<activation>
<property>
@@ -381,7 +384,7 @@ mvn groupId:artifactId:goal -Ddebug=fals
<p><strong>Note</strong>: Environment variables like <code>FOO</code> are
available as properties of the form <code>env.FOO</code>. Further note that
environment variable names are normalized to all upper-case on Windows.</p>
<p>Since Maven 3.9.0 one can also evaluate the POM's packaging value by
referencing property <code>packaging</code>. This is only useful where the
profile activation is defined in a common parent POM which is reused among
multiple Maven projects. The next example will trigger the profile when a
project with packaging <code>war</code> is built:</p>
-<div class="source"><pre class="prettyprint linenums"><code><profiles>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><profiles>
<profile>
<activation>
<property>
@@ -395,7 +398,7 @@ mvn groupId:artifactId:goal -Ddebug=fals
</code></pre></div>Files
<p>This example will trigger the profile when the generated file
<code>target/generated-sources/axistools/wsdl2java/org/apache/maven</code> is
missing.</p>
-<div class="source"><pre class="prettyprint linenums"><code><profiles>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><profiles>
<profile>
<activation>
<file>
@@ -409,7 +412,7 @@ mvn groupId:artifactId:goal -Ddebug=fals
<p>As of Maven 2.0.9, the tags <code><exists></code> and
<code><missing></code> could be interpolated. Supported variables are
system properties like <code>${user.home}</code> and environment variables like
<code>${env.HOME}</code>. Please note that properties and values defined in the
POM itself are not available for interpolation here, e.g. the above example
activator cannot use <code>${project.build.directory}</code> but needs to
hard-code the path <code>target</code>.</p>
<p>Profiles can also be active by default using a configuration like the
following:</p>
-<div class="source"><pre class="prettyprint linenums"><code><profiles>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><profiles>
<profile>
<id>profile-1</id>
<activation>
@@ -487,7 +490,7 @@ mvn groupId:artifactId:goal -Ddebug=fals
<p>All profile elements in a POM from active profiles overwrite the global
elements with the same name of the POM or extend those in case of collections.
In case multiple profiles are active in the same POM or external file, the ones
which are defined <strong>later</strong> take precedence over the ones defined
<strong>earlier</strong> (independent of their profile id and activation
order).</p>
<p>Example:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<repositories>
<repository>
@@ -533,7 +536,7 @@ mvn groupId:artifactId:goal -Ddebug=fals
<h4>External Properties</h4>
<p>External property definition concerns any property value defined outside
the <code>pom.xml</code> but not defined in a corresponding profile inside it.
The most obvious usage of properties in the POM is in plugin configuration.
While it is certainly possible to break project portability without properties,
these critters can have subtle effects that cause builds to fail. For example,
specifying appserver paths in a profile that is specified in the
<code>settings.xml</code> may cause your integration test plugin to fail when
another user on the team attempts to build without a similar
<code>settings.xml</code>. Consider the following <code>pom.xml</code> snippet
for a web application project:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<build>
<plugins>
@@ -553,7 +556,7 @@ mvn groupId:artifactId:goal -Ddebug=fals
</code></pre></div>
<p>Now, in your local <code>${user.home}/.m2/settings.xml</code>, you have:</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
...
<profiles>
<profile>
@@ -577,7 +580,7 @@ mvn groupId:artifactId:goal -Ddebug=fals
<h4>Incomplete Specification of a Natural Profile Set</h4>
<p>In addition to the above portability-breaker, it's easy to fail to cover
all cases with your profiles. When you do this, you're usually leaving one of
your target environments high and dry. Let's take the example
<code>pom.xml</code> snippet from above one more time:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<build>
<plugins>
@@ -597,7 +600,7 @@ mvn groupId:artifactId:goal -Ddebug=fals
</code></pre></div>
<p>Now, consider the following profile, which would be specified inline in the
<code>pom.xml</code>:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<profiles>
<profile>
Modified:
maven/website/content/guides/introduction/introduction-to-repositories.html
==============================================================================
--- maven/website/content/guides/introduction/introduction-to-repositories.html
(original)
+++ maven/website/content/guides/introduction/introduction-to-repositories.html
Sat Feb 18 18:17:30 2023
@@ -209,7 +209,7 @@ under the License.
<h3>Using the Internal Repository</h3>
<p>Using the internal repository is quite simple. Simply make a change to add
a <code>repositories</code> element:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml">
<project>
...
<repositories>
Modified:
maven/website/content/guides/introduction/introduction-to-the-lifecycle.html
==============================================================================
---
maven/website/content/guides/introduction/introduction-to-the-lifecycle.html
(original)
+++
maven/website/content/guides/introduction/introduction-to-the-lifecycle.html
Sat Feb 18 18:17:30 2023
@@ -287,7 +287,7 @@ under the License.
<p>The goals that are configured will be added to the goals already bound to
the lifecycle from the packaging selected. If more than one goal is bound to a
particular phase, the order used is that those from the packaging are executed
first, followed by those configured in the POM. Note that you can use the
<code><executions></code> element to gain more control over the order of
particular goals.</p>
<p>For example, the Modello plugin binds by default its goal
<code>modello:java</code> to the <code>generate-sources</code> phase (Note: The
<code>modello:java</code> goal generates Java source codes). So to use the
Modello plugin and have it generate sources from a model and incorporate that
into the build, you would add the following to your POM in the
<code><plugins></code> section of <code><build></code>:</p>
-<div class="source"><pre class="prettyprint linenums"><code> <plugin>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"> <plugin>
<groupId>org.codehaus.modello</groupId>
<artifactId>modello-maven-plugin</artifactId>
<version>1.8.1</version>
@@ -310,7 +310,7 @@ under the License.
<p>When multiple executions are given that match a particular phase, they are
executed in the order specified in the POM, with inherited executions running
first.</p>
<p>Now, in the case of <code>modello:java</code>, it only makes sense in the
<code>generate-sources</code> phase. But some goals can be used in more than
one phase, and there may not be a sensible default. For those, you can specify
the phase yourself. For example, let's say you have a goal
<code>display:time</code> that echos the current time to the commandline, and
you want it to run in the <code>process-test-resources</code> phase to indicate
when the tests were started. This would be configured like so:</p>
-<div class="source"><pre class="prettyprint linenums"><code> <plugin>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"> <plugin>
<groupId>com.mycompany.example</groupId>
<artifactId>display-maven-plugin</artifactId>
<version>1.0</version>
Modified: maven/website/content/guides/introduction/introduction-to-the-pom.html
==============================================================================
--- maven/website/content/guides/introduction/introduction-to-the-pom.html
(original)
+++ maven/website/content/guides/introduction/introduction-to-the-pom.html Sat
Feb 18 18:17:30 2023
@@ -220,7 +220,7 @@ under the License.
</ul>
<p>Here's an example:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project
xmlns="http://maven.apache.org/POM/4.0.0">
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project
xmlns="http://maven.apache.org/POM/4.0.0">
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
@@ -254,7 +254,7 @@ under the License.
<h5>The Scenario</h5>
<p>As an example, let us reuse our previous artifact,
com.mycompany.app:my-app:1. And let us introduce another artifact,
com.mycompany.app:my-module:1.</p>
-<div class="source"><pre class="prettyprint linenums"><code><project
xmlns="http://maven.apache.org/POM/4.0.0">
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project
xmlns="http://maven.apache.org/POM/4.0.0">
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
@@ -274,7 +274,7 @@ under the License.
<p>Now, if we were to turn com.mycompany.app:my-app:1 into a parent artifact
of com.mycompany.app:my-module:1,we will have to modify
com.mycompany.app:my-module:1's POM to the following configuration:</p>
<p><strong>com.mycompany.app:my-module:1's POM</strong></p>
-<div class="source"><pre class="prettyprint linenums"><code><project
xmlns="http://maven.apache.org/POM/4.0.0">
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project
xmlns="http://maven.apache.org/POM/4.0.0">
<modelVersion>4.0.0</modelVersion>
<parent>
@@ -291,7 +291,7 @@ under the License.
<p>Notice that we now have an added section, the parent section. This section
allows us to specify which artifact is the parent of our POM. And we do so by
specifying the fully qualified artifact name of the parent POM. With this
setup, our module can now inherit some of the properties of our parent POM.</p>
<p>Alternatively, if you want the groupId or the version of your modules to be
the same as their parents, you can remove the groupId or the version identity
of your module in its POM.</p>
-<div class="source"><pre class="prettyprint linenums"><code><project
xmlns="http://maven.apache.org/POM/4.0.0">
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project
xmlns="http://maven.apache.org/POM/4.0.0">
<modelVersion>4.0.0</modelVersion>
<parent>
@@ -319,7 +319,7 @@ under the License.
<h5>The Solution</h5>
<p>To address this directory structure (or any other directory structure), we
would have to add the <code><relativePath></code> element to our parent
section.</p>
-<div class="source"><pre class="prettyprint linenums"><code><project
xmlns="http://maven.apache.org/POM/4.0.0">
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project
xmlns="http://maven.apache.org/POM/4.0.0">
<modelVersion>4.0.0</modelVersion>
<parent>
@@ -348,7 +348,7 @@ under the License.
<p>Given the previous original artifact POMs and directory structure:</p>
<p><strong>com.mycompany.app:my-app:1's POM</strong></p>
-<div class="source"><pre class="prettyprint linenums"><code><project
xmlns="http://maven.apache.org/POM/4.0.0">
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project
xmlns="http://maven.apache.org/POM/4.0.0">
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
@@ -358,7 +358,7 @@ under the License.
</code></pre></div>
<p><strong>com.mycompany.app:my-module:1's POM</strong></p>
-<div class="source"><pre class="prettyprint linenums"><code><project
xmlns="http://maven.apache.org/POM/4.0.0">
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project
xmlns="http://maven.apache.org/POM/4.0.0">
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
@@ -376,7 +376,7 @@ under the License.
<h5>The Solution</h5>
<p>If we are to aggregate my-module into my-app, we would only have to modify
my-app.</p>
-<div class="source"><pre class="prettyprint linenums"><code><project
xmlns="http://maven.apache.org/POM/4.0.0">
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project
xmlns="http://maven.apache.org/POM/4.0.0">
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
@@ -406,7 +406,7 @@ under the License.
<h5>The Solution</h5>
<p>The answer? - the same way as Example 3, by specifying the path to the
module.</p>
-<div class="source"><pre class="prettyprint linenums"><code><project
xmlns="http://maven.apache.org/POM/4.0.0">
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project
xmlns="http://maven.apache.org/POM/4.0.0">
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
@@ -438,7 +438,7 @@ under the License.
<p>Given the previous original artifact POMs again,</p>
<p><strong>com.mycompany.app:my-app:1's POM</strong></p>
-<div class="source"><pre class="prettyprint linenums"><code><project
xmlns="http://maven.apache.org/POM/4.0.0">
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project
xmlns="http://maven.apache.org/POM/4.0.0">
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
@@ -448,7 +448,7 @@ under the License.
</code></pre></div>
<p><strong>com.mycompany.app:my-module:1's POM</strong></p>
-<div class="source"><pre class="prettyprint linenums"><code><project
xmlns="http://maven.apache.org/POM/4.0.0">
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project
xmlns="http://maven.apache.org/POM/4.0.0">
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
@@ -468,7 +468,7 @@ under the License.
<p>To do both project inheritance and aggregation, you only have to apply all
three rules.</p>
<p><strong>com.mycompany.app:my-app:1's POM</strong></p>
-<div class="source"><pre class="prettyprint linenums"><code><project
xmlns="http://maven.apache.org/POM/4.0.0">
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project
xmlns="http://maven.apache.org/POM/4.0.0">
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
@@ -483,7 +483,7 @@ under the License.
</code></pre></div>
<p><strong>com.mycompany.app:my-module:1's POM</strong></p>
-<div class="source"><pre class="prettyprint linenums"><code><project
xmlns="http://maven.apache.org/POM/4.0.0">
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project
xmlns="http://maven.apache.org/POM/4.0.0">
<modelVersion>4.0.0</modelVersion>
<parent>
@@ -502,7 +502,7 @@ under the License.
<p>One of the practices that Maven encourages is <em>don't repeat
yourself</em>. However, there are circumstances where you will need to use the
same value in several different locations. To assist in ensuring the value is
only specified once, Maven allows you to use both your own and pre-defined
variables in the POM.</p>
<p>For example, to access the <code>project.version</code> variable, you would
reference it like so:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
<version>${project.version}</version>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"> <version>${project.version}</version>
</code></pre></div>
<p>One factor to note is that these variables are processed <em>after</em>
inheritance as outlined above. This means that if a parent project uses a
variable, then its definition in the child, not the parent, will be the one
eventually used.</p><section>
<h4>Available Variables</h4><section>
@@ -525,7 +525,7 @@ under the License.
<p>The format of the build timestamp can be customized by declaring the
property <code>maven.build.timestamp.format</code> as shown in the example
below:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project
xmlns="http://maven.apache.org/POM/4.0.0">
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project
xmlns="http://maven.apache.org/POM/4.0.0">
...
<properties>
<maven.build.timestamp.format>yyyy-MM-dd'T'HH:mm:ss'Z'</maven.build.timestamp.format>
@@ -537,7 +537,7 @@ under the License.
<h5>Properties</h5>
<p>You are also able to reference any properties defined in the project as a
variable. Consider the following example:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project
xmlns="http://maven.apache.org/POM/4.0.0">
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project
xmlns="http://maven.apache.org/POM/4.0.0">
...
<properties>
<mavenVersion>3.0</mavenVersion>
Modified: maven/website/content/guides/mini/guide-archive-configuration.html
==============================================================================
--- maven/website/content/guides/mini/guide-archive-configuration.html
(original)
+++ maven/website/content/guides/mini/guide-archive-configuration.html Sat Feb
18 18:17:30 2023
@@ -179,7 +179,7 @@ under the License.
<p>By default, Maven generated archives include the
<code>META-INF/maven</code> directory, which contains the <code>pom.xml</code>
file used to build the archive, and a <code>pom.properties</code> file that
includes some basic properties in a small, easier to read format.</p>
<p>To disable the generation of these files, include the following
configuration for your plugin (in this example, the WAR plugin is used):</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<build>
<plugins>
Modified: maven/website/content/guides/mini/guide-assemblies.html
==============================================================================
--- maven/website/content/guides/mini/guide-assemblies.html (original)
+++ maven/website/content/guides/mini/guide-assemblies.html Sat Feb 18 18:17:30
2023
@@ -176,7 +176,7 @@ under the License.
<h2>Guide to creating assemblies</h2>
<p>The assembly mechanism in Maven provides an easy way to create
distributions using a assembly descriptor and dependency information found in
you POM. In order to use the assembly plug-in you need to configure the
assembly plug-in in your POM and it might look like the following:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
<parent>
<artifactId>maven</artifactId>
<groupId>org.apache.maven</groupId>
@@ -216,7 +216,7 @@ under the License.
<h3>Creating a binary assembly</h3>
<p>This is the most typical usage of the assembly plugin where you are
creating a distribution for standard use.</p>
-<div class="source"><pre class="prettyprint linenums"><code><assembly
xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><assembly
xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2
http://maven.apache.org/xsd/assembly-1.1.2.xsd">
<id>bin</id>
<formats>
@@ -251,7 +251,7 @@ under the License.
<p>You can use a manually defined assembly descriptor as mentioned before but
it is simpler to use the <a
href="/plugins/maven-assembly-plugin/descriptor-refs.html#bin">pre-defined
assembly descriptor bin</a> in such cases.</p>
<p>How to use such pre-defined assembly descriptors is described in the <a
href="/plugins/maven-assembly-plugin/usage.html#configuration">documentation of
maven-assembly-plugin</a>.</p>
-<div class="source"><pre class="prettyprint linenums"><code><assembly
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><assembly
xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2
http://maven.apache.org/xsd/assembly-1.1.2.xsd">
@@ -289,7 +289,7 @@ under the License.
</code></pre></div>
<p>If you like to create a source distribution package the best solution is to
use the <a
href="/plugins/maven-assembly-plugin/descriptor-refs.html#src">pre-defined
assembly descriptor src</a> for such purposes.</p>
-<div class="source"><pre class="prettyprint linenums"><code><assembly
xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><assembly
xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2
http://maven.apache.org/xsd/assembly-1.1.2.xsd">
<id>src</id>
<formats>
Modified: maven/website/content/guides/mini/guide-attached-tests.html
==============================================================================
--- maven/website/content/guides/mini/guide-attached-tests.html (original)
+++ maven/website/content/guides/mini/guide-attached-tests.html Sat Feb 18
18:17:30 2023
@@ -145,7 +145,7 @@ under the License.
<h2>Guide to using attached tests</h2>
<p>You can reuse the tests that you have created for one project in another.
For example, suppose <code>foo-core</code> contains test code in the
<code>${basedir}/src/test/java</code>. To package up those compiled tests in a
JAR and deploy them for general reuse, configure the
<code>maven-jar-plugin</code> as follows:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml">
<project>
<build>
<plugins>
@@ -169,7 +169,7 @@ under the License.
<p>The attached test JAR can be installed and deployed like any other Maven
artifact.</p>
<p>To use the attached test JAR, specify a dependency on the main artifact
with a specified type of <code>test-jar</code> and the
<code>classifier</code>.</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml">
<project>
...
<dependencies>
Modified:
maven/website/content/guides/mini/guide-building-for-different-environments.html
==============================================================================
---
maven/website/content/guides/mini/guide-building-for-different-environments.html
(original)
+++
maven/website/content/guides/mini/guide-building-for-different-environments.html
Sat Feb 18 18:17:30 2023
@@ -205,7 +205,7 @@ src/
<p>In the project descriptor, you need to configure the different profiles.
Only the test profile is showed here.</p></li>
</ul>
-<div class="source"><pre class="prettyprint linenums"><code> <profiles>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"> <profiles>
<profile>
<id>test</id>
<build>
Modified: maven/website/content/guides/mini/guide-configuring-maven.html
==============================================================================
--- maven/website/content/guides/mini/guide-configuring-maven.html (original)
+++ maven/website/content/guides/mini/guide-configuring-maven.html Sat Feb 18
18:17:30 2023
@@ -192,7 +192,7 @@ under the License.
<h3>Configuring your Local Repository</h3>
<p>The location of your local repository can be changed in your user
configuration. The default value is
<code>${user.home}/.m2/repository/</code>.</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
...
<localRepository>/path/to/local/repo/</localRepository>
...
@@ -216,7 +216,7 @@ under the License.
<p>In addition, some repositories may require authorization to download from,
so the corresponding settings can be specified in a <code>server</code> element
in the same way.</p>
<p>Which settings are required will depend on the type of repository you are
deploying to. As of the first release, only SCP deployments and file
deployments are supported by default, so only the following SCP configuration
is needed:</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
...
<servers>
<server>
Modified: maven/website/content/guides/mini/guide-configuring-plugins.html
==============================================================================
--- maven/website/content/guides/mini/guide-configuring-plugins.html (original)
+++ maven/website/content/guides/mini/guide-configuring-plugins.html Sat Feb 18
18:17:30 2023
@@ -176,13 +176,16 @@ under the License.
<li>
<p><a href="#mapping-complex-objects">Mapping Complex Objects</a></p></li>
<li>
-<p><a href="#mapping-collection-types">Mapping Collection Types</a></p></li>
+<p><a href="#mapping-collection-types">Mapping Collection Types</a></p>
+<ul>
+
<li>
<p><a href="#mapping-collections-and-arrays">Mapping Collections and
Arrays</a></p></li>
<li>
<p><a href="#mapping-maps">Mapping Maps</a></p></li>
<li>
<p><a href="#mapping-properties">Mapping Properties</a></p></li>
+</ul></li>
<li>
<p><a href="#configuring-build-plugins">Configuring Build Plugins</a></p></li>
<li>
@@ -214,7 +217,7 @@ under the License.
<h3>Generic Configuration</h3>
<p>Maven plugins (build and reporting) are configured by specifying a
<code><configuration></code> element where the child elements of the
<code><configuration></code> element are mapped to fields, or setters,
inside your Mojo. (Remember that a plug-in consists of one or more Mojos where
a Mojo maps to a goal.) Say, for example, you have a Mojo that performs a query
against a particular URL, with a specified timeout and list of options. The
Mojo might look like the following:</p>
-<div class="source"><pre class="prettyprint linenums"><code>@Mojo( name =
"query" )
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">@Mojo( name = "query" )
public class MyQueryMojo
extends AbstractMojo
{
@@ -236,7 +239,7 @@ public class MyQueryMojo
</code></pre></div>
<p>To configure the Mojo from your POM with the desired URL, timeout and
options you might have something like the following:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<build>
<plugins>
@@ -275,7 +278,7 @@ public class MyQueryMojo
<h5>Mapping Value Objects</h5>
<p>Mapping value types, like Boolean or Integer, is very simple. The
<code><configuration></code> element might look like the following:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<configuration>
<myString>a string</myString>
@@ -350,7 +353,7 @@ public class MyQueryMojo
<h5>Mapping Complex Objects</h5>
<p>Mapping complex types is also fairly straight forward. Let's look at a
simple example where we are trying to map a configuration for Person object.
The <code><configuration></code> element might look like the
following:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<configuration>
<person>
@@ -372,7 +375,7 @@ public class MyQueryMojo
<p>If you wish to have the object to be instantiated live in a different
package or have a more complicated name, specify this using an
<code>implementation</code> attribute like the following:</p></li>
</ul>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<configuration>
<person
implementation="com.mycompany.mojo.query.SuperPerson">
@@ -387,7 +390,7 @@ public class MyQueryMojo
<p>The configuration mapping mechanism can easily deal with most collections
so let's go through a few examples to show you how it's done:</p>Mapping
Collections and Arrays
<p>Mapping to collections works in much the same way as mapping to arrays.
Each item is given in the XML as dedicated element. The element name does not
matter in that case. So if you have a mojo like the following:</p>
-<div class="source"><pre class="prettyprint linenums"><code>public class
MyAnimalMojo
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">public class MyAnimalMojo
extends AbstractMojo
{
@Parameter(property = "animals")
@@ -402,7 +405,7 @@ public class MyQueryMojo
</code></pre></div>
<p>where you have a field named <code>animals</code> then your configuration
for the plug-in would look like the following:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<build>
<plugins>
@@ -430,7 +433,7 @@ public class MyQueryMojo
<p>1 If the element has no children, assume its type is <code>String</code>.
Otherwise, the configuration will fail.</p>
<p>Since Maven 3.3.9 (<a href="https://issues.apache.org/jira/browse/MNG-5440";
class="externalLink">MNG-5440</a>), you can list individual items alternatively
as comma-separated list in the XML value of animals directly. This approach is
also used if configuring collection/array parameters via command line The
following example is equivalent to the example above:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<build>
<plugins>
@@ -449,13 +452,13 @@ public class MyQueryMojo
<p>Each item is mapped again according to the rules of this section depending
on the type of the collection/array.</p>Mapping Maps
<p>In the same way, you could define maps like the following:</p>
-<div class="source"><pre class="prettyprint linenums"><code>...
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">...
@Parameter
private Map<String,String> myMap;
...
</code></pre></div>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<configuration>
<myMap>
@@ -470,13 +473,13 @@ public class MyQueryMojo
<p>In contrast to value objects and collections/arrays there is no string
coercion defined for maps, i.e. you cannot give parameters of that type via CLI
argument.</p>Mapping Properties
<p>Properties should be defined like the following:</p>
-<div class="source"><pre class="prettyprint linenums"><code>...
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">...
@Parameter
private Properties myProperties;
...
</code></pre></div>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<configuration>
<myProperties>
@@ -499,7 +502,7 @@ public class MyQueryMojo
<h4>Using the <code><executions></code> Tag</h4>
<p>You can also configure a mojo using the <code><executions></code>
tag. This is most commonly used for mojos that are intended to participate in
some phases of the <a
href="../introduction/introduction-to-the-lifecycle.html">build lifecycle</a>.
Using <code>MyQueryMojo</code> as an example, you may have something that will
look like:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<build>
<plugins>
@@ -549,7 +552,7 @@ public class MyQueryMojo
<p>Note that while execution id's have to be unique among all executions of a
single plugin within a POM, they don't have to be unique across an inheritance
hierarchy of POMs. Executions of the same id from different POMs are merged.
The same applies to executions that are defined by profiles.</p>
<p>How about if we have a multiple executions with different phases bound to
it? How do you think will it behave? Let us use the example POM above again,
but this time we shall bind <code>execution2</code> to a phase.</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<build>
<plugins>
@@ -587,7 +590,7 @@ public class MyQueryMojo
<p>If there are multiple executions bound to different phases, then the mojo
is executed once for each phase indicated. Meaning, <code>execution1</code>
will be executed applying the configuration setup when the phase of the build
is test, and <code>execution2</code> will be executed applying the
configuration setup when the build phase is already in install.</p>
<p>Now, let us have another mojo example which shows a default lifecycle phase
binding.</p>
-<div class="source"><pre class="prettyprint linenums"><code>@Mojo( name =
"query", defaultPhase = LifecyclePhase.PACKAGE )
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">@Mojo( name = "query", defaultPhase =
LifecyclePhase.PACKAGE )
public class MyBoundQueryMojo
extends AbstractMojo
{
@@ -609,7 +612,7 @@ public class MyBoundQueryMojo
</code></pre></div>
<p>From the above mojo example, <code>MyBoundQueryMojo</code> is by default
bound to the package phase (see the <code>@phase</code> notation). But if we
want to execute this mojo during the install phase and not with package we can
rebind this mojo into a new lifecycle phase using the
<code><phase></code> tag under <code><execution></code>.</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<build>
<plugins>
@@ -649,7 +652,7 @@ public class MyBoundQueryMojo
<p>You could configure the dependencies of the Build plugins, commonly to use
a more recent dependency version.</p>
<p>For instance, the Maven Antrun Plugin version 1.2 uses Ant version 1.6.5,
if you want to use the latest Ant version when running this plugin, you need to
add <code><dependencies></code> element like the following:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<build>
<plugins>
@@ -679,7 +682,7 @@ public class MyBoundQueryMojo
<h4>Using the <code><inherited></code> Tag In Build Plugins</h4>
<p>By default, plugin configuration should be propagated to child POMs, so to
break the inheritance, you could use the <code><inherited></code> tag:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<build>
<plugins>
@@ -704,7 +707,7 @@ public class MyBoundQueryMojo
<h4>Using the <code><reportSets></code> Tag</h4>
<p>You can configure a reporting plugin using the
<code><reportSets></code> tag. This is most commonly used to generate
reports selectively when running <code>mvn site</code>. The following will
generate only the project team report.</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<reporting>
<plugins>
@@ -728,7 +731,7 @@ public class MyBoundQueryMojo
<p><strong>Notes</strong>:</p>
<p>1 To exclude all reports, you need to use:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
<reportSets>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"> <reportSets>
<reportSet>
<reports/>
</reportSet>
@@ -738,7 +741,7 @@ public class MyBoundQueryMojo
<h4>Using the <code><inherited></code> Tag In Reporting Plugins</h4>
<p>Similar to the build plugins, to break the inheritance, you can use the
<code><inherited></code> tag:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<reporting>
<plugins>
Modified: maven/website/content/guides/mini/guide-creating-archetypes.html
==============================================================================
--- maven/website/content/guides/mini/guide-creating-archetypes.html (original)
+++ maven/website/content/guides/mini/guide-creating-archetypes.html Sat Feb 18
18:17:30 2023
@@ -176,7 +176,7 @@ under the License.
<h3>1. Create a new project and pom.xml for the archetype artifact</h3>
<p>An example <code>pom.xml</code> for an archetype artifact looks as
follows:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml">
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
@@ -202,7 +202,7 @@ under the License.
<h3>2. Create the archetype descriptor</h3>
<p>The <a
href="/archetype/archetype-models/archetype-descriptor/archetype-descriptor.html">archetype
descriptor</a> is a file called <code>archetype-metadata.xml</code> which must
be located in the <code>src/main/resources/META-INF/maven/</code> directory. An
example of an archetype descriptor can be found in the quickstart archetype:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml">
<archetype-descriptor
xmlns="http://maven.apache.org/plugins/maven-archetype-plugin/archetype-descriptor/1.1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/plugins/maven-archetype-plugin/archetype-descriptor/1.1.0
https://maven.apache.org/xsd/archetype-descriptor-1.1.0.xsd"
@@ -233,7 +233,7 @@ under the License.
<p>At this point one can only specify individual files to be created but not
empty directories.</p>
<p>Thus the quickstart archetype shown above defines the following directory
structure:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml">
archetype
|-- pom.xml
`-- src
@@ -257,7 +257,7 @@ archetype
<p>The next component of the archetype to be created is the prototype
<code>pom.xml</code>. Any <code>pom.xml</code> will do, just don't forget to
the set <code>artifactId</code> and <code>groupId</code> as variables (
<code>${artifactId}</code> / <code>${groupId}</code> ). Both variables will be
initialized from the commandline when calling
<code>archetype:generate</code>.</p>
<p>An example for a prototype <code>pom.xml</code> is:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml">
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
Modified: maven/website/content/guides/mini/guide-default-execution-ids.html
==============================================================================
--- maven/website/content/guides/mini/guide-default-execution-ids.html
(original)
+++ maven/website/content/guides/mini/guide-default-execution-ids.html Sat Feb
18 18:17:30 2023
@@ -179,7 +179,7 @@ under the License.
<p>Consider the case where the user wants to execute the
<code>assembly:assembly</code> mojo directly on the command line, but already
has a configuration for the <code>assembly:single</code> mojo that runs during
the main build lifecycle. Since these configurations require different options,
the user cannot use the plugin-level configuration section to specify common
elements.</p>
<p>In this case, the assembly-plugin configuration might look like this:</p>
-<div class="source"><pre class="prettyprint linenums"><code><plugin>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><plugin>
<artifactId>maven-assembly-plugin</artifactId>
<configuration>
<tarLongFileMode>gnu</tarLongFileMode>
@@ -217,7 +217,7 @@ under the License.
<p>Therefore, the user needs to compile the bulk of his application to target
the 1.5 Java specification, then compile the rest (the entry point) to target
an older specification…say, 1.3. The first execution will specify the
<code>source</code> and <code>target</code> values at <code>1.5</code>, and add
an <code>excludes</code> section to avoid compiling the entry point for the
application. The second pass will then re-specify <code>source</code> and
<code>target</code> to <code>1.3</code>, and basically invert the original
<code>excludes</code> section to be an <code>includes</code> section, so as to
compile <em>only</em> the entry point class.</p>
<p>The resulting configuration might look something like this:</p>
-<div class="source"><pre class="prettyprint linenums"><code><plugin>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><plugin>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.5</source>
@@ -263,7 +263,7 @@ under the License.
<p>Finally, building on our use of the compiler plugin to tease out these
different use cases, consider the case where a user wants to target version 1.4
of the Java specification as his runtime platform. However, he still wants the
convenience and other advantages to be found in a unit-testing framework like
TestNG. This forces the user to configure the <code>compile</code> mojo with
one set of <code>source</code> and <code>target</code> values - specifically,
<code>1.4</code> - and the <code>testCompile</code> mojo with another
(<code>1.5</code>).</p>
<p>The resulting compiler-plugin configuration might look something like the
following:</p>
-<div class="source"><pre class="prettyprint linenums"><code><plugin>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><plugin>
<artifactId>maven-compiler-plugin</artifactId>
<executions>
<execution>
Modified:
maven/website/content/guides/mini/guide-deployment-security-settings.html
==============================================================================
--- maven/website/content/guides/mini/guide-deployment-security-settings.html
(original)
+++ maven/website/content/guides/mini/guide-deployment-security-settings.html
Sat Feb 18 18:17:30 2023
@@ -176,7 +176,7 @@ under the License.
<p>In addition, some repositories may require authorisation to download from,
so the corresponding settings can be specified in a server element in the same
way.</p>
<p>Which settings are required will depend on the type of repository you are
deploying to. As of the first release, only SCP deployments and file
deployments are supported by default, so only the following SCP configuration
is needed:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml">
<settings>
.
.
Modified: maven/website/content/guides/mini/guide-encryption.html
==============================================================================
--- maven/website/content/guides/mini/guide-encryption.html (original)
+++ maven/website/content/guides/mini/guide-encryption.html Sat Feb 18 18:17:30
2023
@@ -218,7 +218,7 @@ under the License.
</code></pre></div>
<p>Store this password in the
<code>${user.home}/.m2/settings-security.xml</code>; it should look like</p>
-<div class="source"><pre class="prettyprint
linenums"><code><settingsSecurity>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settingsSecurity>
<master>{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+9EF1iFQyJQ=}</master>
</settingsSecurity>
</code></pre></div>
@@ -235,7 +235,7 @@ under the License.
</code></pre></div>
<p>Copy and paste it into the servers section of your
<code>settings.xml</code> file. This will look like:</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
...
<servers>
...
@@ -251,7 +251,7 @@ under the License.
</code></pre></div>
<p>Please note that password can contain any information outside of the curly
brackets, so that the following will still work:</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
...
<servers>
...
@@ -274,14 +274,14 @@ under the License.
<h3>How to keep the master password on removable drive</h3>
<p>Create the master password exactly as described above, and store it on a
removable drive, for instance on OSX, my USB drive mounts as
<code>/Volumes/mySecureUsb</code>, so I store</p>
-<div class="source"><pre class="prettyprint
linenums"><code><settingsSecurity>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settingsSecurity>
<master>{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+9EF1iFQyJQ=}</master>
</settingsSecurity>
</code></pre></div>
<p>in the file
<code>/Volumes/mySecureUsb/secure/settings-security.xml</code></p>
<p>And then I create <code>${user.home}/.m2/settings-security.xml</code> with
the following content:</p>
-<div class="source"><pre class="prettyprint
linenums"><code><settingsSecurity>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settingsSecurity>
<relocation>/Volumes/mySecureUsb/secure/settings-security.xml</relocation>
</settingsSecurity>
</code></pre></div>
Modified: maven/website/content/guides/mini/guide-generating-sources.html
==============================================================================
--- maven/website/content/guides/mini/guide-generating-sources.html (original)
+++ maven/website/content/guides/mini/guide-generating-sources.html Sat Feb 18
18:17:30 2023
@@ -177,7 +177,7 @@ under the License.
<p>Let's run though a short example to try and help. To generate sources you
must first have a plugin that participates in the <code>generate-sources</code>
phase like the <a href="http://www.antlr.org/api/maven-plugin/latest/";
class="externalLink">ANTLR4 Maven Plugin</a>.</p>
<p>So this is all fine and dandy, we have a plugin that wants to generate some
sources from a Antlr4 grammar but how do we use it. You need to specify that
you want to use it in your POM:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml">
<project>
...
<build>
Modified: maven/website/content/guides/mini/guide-http-settings.html
==============================================================================
--- maven/website/content/guides/mini/guide-http-settings.html (original)
+++ maven/website/content/guides/mini/guide-http-settings.html Sat Feb 18
18:17:30 2023
@@ -193,7 +193,9 @@ under the License.
<li>
<p><a href="#taking-control-of-your-http-headers">Taking Control of Your HTTP
Headers</a></p></li>
<li>
-<p><a href="#fine-tuning-httpclient-parameters">Fine-Tuning HttpClient
Parameters</a></p></li>
+<p><a href="#fine-tuning-httpclient-parameters">Fine-Tuning HttpClient
Parameters</a></p>
+<ul>
+
<li>
<p><a href="#non-string-parameter-values">Non-String Parameter
Values</a></p></li>
<li>
@@ -202,6 +204,7 @@ under the License.
<p><a
href="#example--lifting-auth-scope-restriction-for-external-authentication-systems">Example:
Lifting auth scope restriction for external authentication systems</a></p></li>
<li>
<p><a href="#ignoring-cookies">Ignoring Cookies</a></p></li>
+</ul></li>
<li>
<p><a href="#support-for-general-wagon-configuration-standards">Support for
General-Wagon Configuration Standards</a></p>
<ul>
@@ -223,7 +226,7 @@ under the License.
<h4>HTTP Headers</h4>
<p>In all HTTP transports, you can add your custom HTTP headers like this:</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
<servers>
<server>
<id>my-server</id>
@@ -243,7 +246,7 @@ under the License.
<h4>Connection Timeouts</h4>
<p>All transport implementations that perform some network access allow the
configuration of a several timeouts, for example to allow the user to tell
Maven how long to wait before giving up on a connection that has not
responded.</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
<servers>
<server>
<id>my-server</id>
@@ -304,7 +307,7 @@ problems with HTTP servers and proxies t
<h4>Configuring GET, HEAD, PUT, or All of the Above</h4>
<p>In all of the examples below, it's important to understand that you can
configure the HTTP settings for all requests made to a given server, or for
only one method. To configure all methods for a server, use the following
section of the <code>settings.xml</code> file:</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
[...]
<servers>
<server>
@@ -322,7 +325,7 @@ problems with HTTP servers and proxies t
</code></pre></div>
<p>On the other hand, if you can live with the default configuration for most
requests - say, HEAD and GET requests, which are used to check for the
existence of a file and retrieve a file respectively - maybe you only need to
configure the PUT method:</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
[...]
<servers>
<server>
@@ -343,7 +346,7 @@ problems with HTTP servers and proxies t
<p>As you may have noticed above, the default HTTP headers do have the
potential to cause problems. For instance, some websites set the encoding for
downloading GZipped files as <code>gzip</code>, in spite of the fact that the
HTTP request itself isn't being sent using GZip compression. If the client is
using the <code>Accept-Encoding: gzip</code> header, this can result in the
client itself decompressing the GZipped file <em>during the transfer</em> and
writing the decompressed file to the local disk with the original filename.
This can be misleading to say the least, and can use up an inordinate amount of
disk space on the local computer.</p>
<p>To turn off this default behavior, simply disable the default headers.
Then, respecify the other headers that you are still interested in, like
this:</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
[...]
<servers>
<server>
@@ -403,7 +406,7 @@ problems with HTTP servers and proxies t
<h5>Example: Using Preemptive Authentication</h5>
<p>Using the above syntax, you can configure preemptive authentication for PUT
requests using the boolean HttpClient parameter
<code>http.authentication.preemptive</code>, like this:</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
<servers>
<server>
<id>my-server</id>
@@ -425,7 +428,7 @@ problems with HTTP servers and proxies t
</code></pre></div>
<p>Another option is to make write it like this:</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
<servers>
<server>
<id>my-server</id>
@@ -441,11 +444,11 @@ problems with HTTP servers and proxies t
</settings>
</code></pre></div></section><section>
<h5>Example: Lifting auth scope restriction for external authentication
systems</h5>
-<p>Maven Wagon by default limits supplied credentials to the host:port
combination scope, ignoring any other target servers. When the target server
delegates authentication to an external system, you need to deliberately lift
that scope limitation. Configure your server element to pass authentication to
all target servers which challenge the client. +—+ <em>settings</em>
<em>servers</em> <em>server</em> <em>id_my-server</em>/id_
<em>configuration</em> <em>basicAuthScope</em> <em>host_ANY</em>/host_
<em>port_ANY</em>/port_ <em>!– or even 443 to force the use of TLS
–</em> <em>/basicAuthScope</em> <em>httpConfiguration</em> <em>all</em>
<em>params</em> <em>property</em>
<em>name_http.protocol.cookie-policy</em>/name_ <em>value_standard</em>/value_
<em>/property</em> <em>/params</em> <em>/all</em> <em>/httpConfiguration</em>
<em>/configuration</em> <em>/server</em> <em>/servers</em> <em>/settings</em>
+—+</p></section><section>
+<p>Maven Wagon by default limits supplied credentials to the host:port
combination scope, ignoring any other target servers. When the target server
delegates authentication to an external system, you need to deliberately lift
that scope limitation. Configure your server element to pass authentication to
all target servers which challenge the client. +—+ <em>settings</em>
<em>servers</em> <em>server</em>
<em>id_my-server</em>/id__configuration__basicAuthScope__host_ANY_/host_
<em>port_ANY</em>/port__!– or even 443 to force the use of TLS
–<strong>/basicAuthScope__httpConfiguration__all__params__property__name_http.protocol.cookie-policy_/name_
<em>value_standard</em>/value</strong>/property__/params__/all__/httpConfiguration__/configuration__/server__/servers__/settings_
+—+</p></section><section>
<h5>Ignoring Cookies</h5>
<p>Like the example above, telling the HttpClient to ignore cookies for all
methods of request is a simple matter of configuring the
<code>http.protocol.cookie-policy</code> parameter (it uses a regular string
value, so no special syntax is required):</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
<servers>
<server>
<id>my-server</id>
@@ -471,7 +474,7 @@ problems with HTTP servers and proxies t
<h5>HTTP Headers</h5>
<p>In all HTTP Wagon implementations, you can add your own HTTP headers like
this:</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
<servers>
<server>
<id>my-server</id>
@@ -491,7 +494,7 @@ problems with HTTP servers and proxies t
<h5>Connection Timeouts</h5>
<p>All wagon implementations that extend the <code>AbstractWagon</code> class,
including those for SCP, HTTP, FTP, and more, allow the configuration of a
connection timeout, to allow the user to tell Maven how long to wait before
giving up on a connection that has not responded. This option is preserved in
the HttpClient-based wagon, but this wagon also provides a fine-grained
alternative configuration that can allow you to specify timeouts per-method for
a given server. The old configuration option - which is still supported - looks
like this:</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
<servers>
<server>
<id>my-server</id>
@@ -504,7 +507,7 @@ problems with HTTP servers and proxies t
</code></pre></div>
<p>…while the new configuration option looks more like this:</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
<servers>
<server>
<id>my-server</id>
@@ -523,7 +526,7 @@ problems with HTTP servers and proxies t
<h5>Read time out</h5>
<p>With Wagon 2.0 and Apache Maven 3.0.4, a default timeout of 30 minutes
comes by default. If you want to change this value, you can add the following
setup in your settings:</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
<servers>
<server>
<id>my-server</id>
Modified:
maven/website/content/guides/mini/guide-large-scale-centralized-deployments.html
==============================================================================
---
maven/website/content/guides/mini/guide-large-scale-centralized-deployments.html
(original)
+++
maven/website/content/guides/mini/guide-large-scale-centralized-deployments.html
Sat Feb 18 18:17:30 2023
@@ -215,7 +215,7 @@ under the License.
<p>Maven can be instructed to download artifacts from the repository manager's
virtual repository by defining a mirror in the Maven <code>settings.xml</code>
file as described in the <a href="./guide-mirror-settings.html">Guide to Mirror
Settings</a>.</p>
<p>Example: To download artifacts from the corporate repository manager's
<code>maven-virtual</code> repository:</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
...
<mirrors>
<!-- Mirror all external repositories via the Corporate Repository
Manager's Maven virtual repository -->
@@ -237,7 +237,7 @@ under the License.
<p>Typically, only continuous integration servers are allowed to upload
artifacts to the repository manager. Therefore, these settings should only be
specified in <code>settings.xml</code> files on continuous integration servers,
and should not be in <code>settings.xml</code> files on developer machines.
Alternatively, if you want developers to be able to upload artifacts to the
repository manager, then include these properties in the
<code>settings.xml</code> files used by developers.</p>
<p>Example: To upload artifacts to one of the corporate repository manager's
hosted repositories:</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
...
<profiles>
<profile>
Modified: maven/website/content/guides/mini/guide-maven-classloading.html
==============================================================================
--- maven/website/content/guides/mini/guide-maven-classloading.html (original)
+++ maven/website/content/guides/mini/guide-maven-classloading.html Sat Feb 18
18:17:30 2023
@@ -224,7 +224,7 @@ under the License.
<p>Plugins marked with <code><extensions>true</extensions></code>
leverage the Build Extension classloader instead of the Plugin classloader.</p>
<p>Users can add dependencies to this classloader by adding dependencies to a
plugin in the
<code>[plugins/plugin](/ref/current/maven-model/maven.html#class_plugin)</code>
section of their project <code>pom.xml</code>. Here is a sample of adding
<code>ant-nodeps</code> to the plugin classloader of the Antrun Plugin and
hereby enabling the use of additional/optional Ant tasks:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
<plugin>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"> <plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.3</version>
Modified: maven/website/content/guides/mini/guide-mirror-settings.html
==============================================================================
--- maven/website/content/guides/mini/guide-mirror-settings.html (original)
+++ maven/website/content/guides/mini/guide-mirror-settings.html Sat Feb 18
18:17:30 2023
@@ -185,7 +185,7 @@ under the License.
</ul>
<p>To configure a mirror of a given repository, you provide it in your
settings file (<code>${user.home}/.m2/settings.xml</code>), giving the new
repository its own <code>id</code> and <code>url</code>, and specify the
<code>mirrorOf</code> setting that is the ID of the repository you are using a
mirror of. For example, the ID of the main Maven Central repository included by
default is <code>central</code>, so to use the different mirror instance, you
would configure the following:</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
...
<mirrors>
<mirror>
@@ -207,7 +207,7 @@ under the License.
<p>To achieve this, set <code>mirrorOf</code> to <code>\*</code>.</p>
<p><strong>Note:</strong> This feature is only available in Maven 2.0.5+.</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
...
<mirrors>
<mirror>
@@ -252,7 +252,7 @@ under the License.
<p><code>*,!repo1</code> = everything except repo1</p></li>
</ul>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
...
<mirrors>
<mirror>
Modified: maven/website/content/guides/mini/guide-multiple-repositories.html
==============================================================================
--- maven/website/content/guides/mini/guide-multiple-repositories.html
(original)
+++ maven/website/content/guides/mini/guide-multiple-repositories.html Sat Feb
18 18:17:30 2023
@@ -174,7 +174,7 @@ under the License.
<h2>Setting up Multiple Repositories</h2>
<p>There are two different ways that you can specify the use of multiple
repositories. The first way is to specify in a POM which repositories you want
to use. That is supported both inside and outside of build profiles:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml">
<project>
...
<repositories>
@@ -196,7 +196,7 @@ under the License.
<p><strong>NOTE:</strong> You will also get the standard set of repositories
as defined in the <a
href="../introduction/introduction-to-the-pom.html#Super_POM">Super POM</a>.</p>
<p>The other way you can specify multiple repositories is by creating a
profile in the <code>${user.home}/.m2/settings.xml</code> or
<code>${maven.home}/conf/settings.xml</code> file like the following:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml">
<settings>
...
<profiles>
Modified: maven/website/content/guides/mini/guide-proxies.html
==============================================================================
--- maven/website/content/guides/mini/guide-proxies.html (original)
+++ maven/website/content/guides/mini/guide-proxies.html Sat Feb 18 18:17:30
2023
@@ -175,7 +175,7 @@ under the License.
<p>You can configure a proxy to use for some or all of your HTTP requests with
Maven. The username and password are only required if your proxy requires basic
authentication (note that later releases may support storing your passwords in
a secured keystore - in the mean time, please ensure your settings.xml file
(usually <code>${user.home}/.m2/settings.xml</code>) is secured with
permissions appropriate for your operating system).</p>
<p>The <code>nonProxyHosts</code> setting accepts wild cards, and each host
not to proxy is separated by the | character. This matches the JDK
configuration equivalent.</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml">
<settings>
.
.
Modified: maven/website/content/guides/mini/guide-releasing.html
==============================================================================
--- maven/website/content/guides/mini/guide-releasing.html (original)
+++ maven/website/content/guides/mini/guide-releasing.html Sat Feb 18 18:17:30
2023
@@ -204,7 +204,7 @@ under the License.
</ul>
<p>The previous goal parameters can be supplied while executing maven on the
commandline, (as shown in the previous example) or they can be defined and
maintained within the project's <em>pom.xml</em> file. The location of the
current development trunk is defined within the <em>pom.xml</em> file in the
following form:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
<artifactId>app</artifactId>
@@ -239,7 +239,7 @@ under the License.
</code></pre></div>
<p>To define the tagBase parameter within the <em>pom.xml</em> file a tagBase
element must be defined within a <em>plugins/plugin/configuration</em> element.
The following example shows how this would look within the <em>pom.xml</em>
file.</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
<artifactId>app</artifactId>
@@ -318,7 +318,7 @@ checkpoint.check-in-development-version=
<p>During the execution of the <code>release:perform</code> goal the entire
maven build lifecycle is executed on the project. The tagged project source
code is extracted, compiled, tested, documented and deployed. An instance of
the release artifact is deployed to the machine's local repository. An another
instance of the release can be deployed to a remote repository by configuring
the <em>distributionManagement</em> element within the <em>pom.xml</em>
file.</p>
<p>The following is an example of how a distributionManagement element can be
configured within a project <em>pom.xml</em> file.</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
<artifactId>app</artifactId>
Modified: maven/website/content/guides/mini/guide-relocation.html
==============================================================================
--- maven/website/content/guides/mini/guide-relocation.html (original)
+++ maven/website/content/guides/mini/guide-relocation.html Sat Feb 18 18:17:30
2023
@@ -185,7 +185,7 @@ under the License.
<p><strong>Note:</strong> Before you replace your old POM files in
<code>/bar/foo/</code> with these minimal POM files, make sure you have made
backups!</p>
<p>The minimal POM file might look like this for version 1.0 of
<code>foo</code>:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
<modelVersion>4.0.0</modelVersion>
<groupId>bar</groupId>
<artifactId>foo</artifactId>
Modified: maven/website/content/guides/mini/guide-repository-ssl.html
==============================================================================
--- maven/website/content/guides/mini/guide-repository-ssl.html (original)
+++ maven/website/content/guides/mini/guide-repository-ssl.html Sat Feb 18
18:17:30 2023
@@ -198,7 +198,7 @@ under the License.
<h4>Storing certificate</h4>
<p>The following command line imports the certififcate authority's certificate
into a JKS formatted key store named <code>trust.jks</code>, the <em>trust
store</em>.</p>
-<div class="source"><pre class="prettyprint linenums"><code>$> keytool -v
-alias mavensrv -import \
+<div class="source"><pre class="prettyprint linenums"><code
class="language-bash">$> keytool -v -alias mavensrv -import \
-file /somewhere/in/filesystem/CACert.cert\
-keystore trust.jks
Enter keystore password:
@@ -226,7 +226,7 @@ $>
<p>Not all the properties must be set depending of your precise settings: type
of store may left to default, password may be empty.</p>
<p>They may be set either on maven's command-line, in <code>.mavenrc</code>
file or in <code>MAVEN_OPTS</code> environment variable. For the setting
defined in this document, here is an example <code>.mavenrc</code> file:</p>
-<div class="source"><pre class="prettyprint
linenums"><code>MAVEN_OPTS="-Xmx512m -Djavax.net.ssl.trustStore=trust.jks \
+<div class="source"><pre class="prettyprint linenums"><code
class="language-bash">MAVEN_OPTS="-Xmx512m
-Djavax.net.ssl.trustStore=trust.jks \
-Djavax.net.ssl.trustStorePassword= \
-Djavax.net.ssl.keyStore=/home/directory/mycertificate.p12 \
-Djavax.net.ssl.keyStoreType=pkcs12 \
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 Sat Feb 18
18:17:30 2023
@@ -185,7 +185,7 @@ under the License.
</code></pre></div>
<p>1 Enable Reproducible Builds mode for plugins, by adding <a
href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74682318#Reproducible/VerifiableBuilds-OutputArchiveEntriesTimestamp";
class="externalLink"><code>project.build.outputTimestamp</code> property</a>
to the project's <code>pom.xml</code>:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
<properties>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"> <properties>
<project.build.outputTimestamp>2023-01-01T00:00:00Z</project.build.outputTimestamp>
</properties>
</code></pre></div>
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 Sat Feb 18 18:17:30 2023
@@ -214,7 +214,7 @@ under the License.
<h4>Classical Website deployment</h4>
<p>To be able to deploy the site with a classical network protocol (ftp, scp,
webdav), you must first declare a location to distribute to in your
<code>pom.xml</code>, similar to the repository for deployment:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<distributionManagement>
<site>
@@ -240,7 +240,7 @@ under the License.
<p>When site publication is done with a SCM commit, like with <a
href="https://pages.github.com/"; class="externalLink">GitHub Pages</a> or <a
href="https://infra.apache.org/project-site.html#tools";
class="externalLink">Apache svnpubsub/gitpubsub</a>, deploying the site will be
done with <a href="/plugins/maven-scm-publish-plugin/">Maven SCM Publish
Plugin</a>.</p>
<p>For example with a project hosted on GitHub and using GitHub Pages for its
site publication:</p>
-<div class="source"><pre class="prettyprint linenums"><code> <plugin>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"> <plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-scm-publish-plugin</artifactId>
<version>3.1.0</version>
@@ -256,7 +256,7 @@ under the License.
<h3>Creating a Site Descriptor</h3>
<p>The <code>site.xml</code> file is used to describe the structure of the
site. A sample is given below:</p>
-<div class="source"><pre class="prettyprint linenums"><code><?xml
version="1.0" encoding="ISO-8859-1"?>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><?xml version="1.0"
encoding="ISO-8859-1"?>
<project xmlns="http://maven.apache.org/DECORATION/1.8.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/DECORATION/1.8.0
https://maven.apache.org/xsd/decoration-1.8.0.xsd"
name="Maven">
@@ -331,7 +331,7 @@ under the License.
<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 Project Info Reports
plugin to a special <code><reporting></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"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<reporting>
<plugins>
@@ -353,7 +353,7 @@ under the License.
<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>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<build>
<plugins>
Modified: maven/website/content/guides/mini/guide-snippet-macro.html
==============================================================================
--- maven/website/content/guides/mini/guide-snippet-macro.html (original)
+++ maven/website/content/guides/mini/guide-snippet-macro.html Sat Feb 18
18:17:30 2023
@@ -171,7 +171,7 @@ under the License.
<h3>Snippets in Sources</h3><section>
<h4>Java</h4>
-<div class="source"><pre class="prettyprint linenums"><code> // START
SNIPPET: snip-id
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java"> // START SNIPPET: snip-id
public static void main( String[] args )
{
System.out.println( "Hello World!" );
@@ -180,7 +180,7 @@ under the License.
</code></pre></div></section><section>
<h4>XML</h4>
-<div class="source"><pre class="prettyprint linenums"><code> <!-- START
SNIPPET: snip-id -->
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"> <!-- START SNIPPET: snip-id -->
<navigation-rule>
<from-view-id>/logon.jsp</from-view-id>
<navigation-case>
Modified: maven/website/content/guides/mini/guide-using-ant.html
==============================================================================
--- maven/website/content/guides/mini/guide-using-ant.html (original)
+++ maven/website/content/guides/mini/guide-using-ant.html Sat Feb 18 18:17:30
2023
@@ -176,7 +176,7 @@ under the License.
<h2>Guide to using Ant with Maven</h2>
<p>The example above illustrates how to bind an ant script to a lifecycle
phase. You can add a script to each lifecycle phase, by duplicating the
<em>execution/</em> section and specifying a new phase.</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml">
<project>
<modelVersion>4.0.0</modelVersion>
<artifactId>my-test-app</artifactId>
@@ -214,7 +214,7 @@ under the License.
</code></pre></div>
<p>So a concrete example would be something like the following:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml">
<project>
<modelVersion>4.0.0</modelVersion>
<artifactId>my-test-app</artifactId>
Modified: maven/website/content/guides/mini/guide-using-extensions.html
==============================================================================
--- maven/website/content/guides/mini/guide-using-extensions.html (original)
+++ maven/website/content/guides/mini/guide-using-extensions.html Sat Feb 18
18:17:30 2023
@@ -197,7 +197,7 @@ under the License.
<p>Example:</p></li>
</ul>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml">
<project>
...
<build>
@@ -223,7 +223,7 @@ under the License.
<p>Example:</p></li>
</ul>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml">
<project>
...
<build>
Modified: maven/website/content/guides/mini/guide-wagon-providers.html
==============================================================================
--- maven/website/content/guides/mini/guide-wagon-providers.html (original)
+++ maven/website/content/guides/mini/guide-wagon-providers.html Sat Feb 18
18:17:30 2023
@@ -185,7 +185,7 @@ under the License.
<h3><code>settings.xml</code> Configuration</h3>
<p>To specify which Wagon provider to use for a particular server, modify your
<code>settings.xml</code> file to add the <code><wagonProvider></code>
configuration to your <code><server></code> entry, like the following:</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><settings>
[...]
<servers>
<server>
@@ -199,7 +199,7 @@ under the License.
<h3>Available Wagon Providers</h3>
<p>Maven 2.2.1 provides two providers for HTTP/HTTPS Wagons:
<code>lightweight</code> and <code>httpclient</code>. If you add a new HTTP
Wagon implementation via build extension, you'll need to make sure the
extension binds its Wagon components to role-hints of the form
<code><protocol>-<provider></code> in order to allow users to
specify your alternative Wagon provider. For instance, the HttpClient HTTP
Wagon component definition looks like this:</p>
-<div class="source"><pre class="prettyprint linenums"><code><component>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><component>
<role>org.apache.maven.wagon.Wagon</role>
<role-hint>http-httpclient</role-hint>
<implementation>org.apache.maven.wagon.providers.http.HttpWagon</implementation>
