Modified: maven/website/content/guides/plugin/guide-java-plugin-development.html
==============================================================================
--- maven/website/content/guides/plugin/guide-java-plugin-development.html
(original)
+++ maven/website/content/guides/plugin/guide-java-plugin-development.html Sat
Feb 18 18:17:30 2023
@@ -205,7 +205,7 @@ Any class with this annotation are inclu
<p>Listed below is a simple mojo class which has no parameters. This is about
as simple as a mojo can be.
After the listing is a description of the various parts of the source.</p>
-<div class="source"><pre class="prettyprint linenums"><code>package
sample.plugin;
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">package sample.plugin;
import org.apache.maven.plugin.AbstractMojo;
import org.apache.maven.plugin.MojoExecutionException;
@@ -262,7 +262,7 @@ This logger is the accepted means to dis
<p>Listed below is an illustration of the sample mojo project's pom with the
parameters set as described in the above table:</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>sample.plugin</groupId>
@@ -345,7 +345,7 @@ This logger is the accepted means to dis
<p>The most direct means of executing your new plugin is to specify the plugin
goal directly on the command line.
To do this, you need to configure the <code>hello-maven-plugin</code> plugin
in you project:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<build>
<pluginManagement>
@@ -381,7 +381,7 @@ You may also assign one through addition
To do this, you need to add the following to your
<code>${user.home}/.m2/settings.xml</code> file:</li>
</ul>
-<div class="source"><pre class="prettyprint
linenums"><code><pluginGroups>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><pluginGroups>
<pluginGroup>sample.plugin</pluginGroup>
</pluginGroups>
</code></pre></div>
@@ -389,7 +389,7 @@ To do this, you need to add the followin
<h3>Attaching the Mojo to the Build Lifecycle</h3>
<p>You can also configure your plugin to attach specific goals to a particular
phase of the build lifecycle. Here is an example:</p>
-<div class="source"><pre class="prettyprint linenums"><code> <build>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"> <build>
<pluginManagement>
<plugins>
<plugin>
@@ -436,7 +436,7 @@ To do this, you need to add the followin
<p>Defining a parameter is as simple as creating an instance variable in the
mojo and adding the proper annotations.
Listed below is an example of a parameter for the simple mojo:</p>
-<div class="source"><pre class="prettyprint linenums"><code> /**
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java"> /**
* The greeting to display.
*/
@Parameter( property = "sayhi.greeting", defaultValue =
"Hello World!" )
@@ -452,7 +452,7 @@ This value can include expressions which
<p>Configuring the parameter values for a plugin is done in a Maven project
within the <code>pom.xml</code> file as part of defining the plugin in the
project.
An example of configuring a plugin:</p>
-<div class="source"><pre class="prettyprint linenums"><code><plugin>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><plugin>
<groupId>sample.plugin</groupId>
<artifactId>hello-maven-plugin</artifactId>
<version>1.0-SNAPSHOT</version>
@@ -469,7 +469,7 @@ An example of configuring a plugin:</p>
<p>You can also add <code>@Parameter</code> annotation on setter method (from
version 3.7.0 of <code>plugin-tools</code>)</p>
<p>So our Mojo would look like the following:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">
public class MyQueryMojo extends AbstractMojo {
// provide name for non matching field and setter name
Modified:
maven/website/content/guides/plugin/guide-java-report-plugin-development.html
==============================================================================
---
maven/website/content/guides/plugin/guide-java-report-plugin-development.html
(original)
+++
maven/website/content/guides/plugin/guide-java-report-plugin-development.html
Sat Feb 18 18:17:30 2023
@@ -163,7 +163,7 @@ under the License.
<h3>How It Works</h3>
<p>1 A regular Maven project usually invokes <em>reporting goals</em> of a
plugin by declaring such plugin in the <a
href="/plugins/maven-site-plugin/examples/configuring-reports.html"><code><reporting></code></a>
section of its <code>pom.xml</code> as in the example below:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<reporting>
<plugins>
@@ -228,7 +228,7 @@ under the License.
<p>The below examples can be copied and pasted as a template.</p><section>
<h4>./pom.xml</h4>
-<div class="source"><pre class="prettyprint linenums"><code><project
xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+<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
http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
@@ -330,7 +330,7 @@ under the License.
</code></pre></div></section><section>
<h4>./src/main/java/com/mycompany/maven/SimpleReport.java</h4>
-<div class="source"><pre class="prettyprint linenums"><code>package
com.mycompany.maven;
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">package com.mycompany.maven;
import java.util.Locale;
@@ -432,7 +432,7 @@ public class SimpleReport extends Abstra
<h4>Building the Simple Plugin</h4>
<p>Building the plugin is done by executing the below command in the root
directory of the plugin project:</p>
-<div class="source"><pre class="prettyprint linenums"><code>$ mvn install
+<div class="source"><pre class="prettyprint linenums"><code>mvn install
</code></pre></div>
<p>This command will:</p>
<ul>
@@ -446,7 +446,7 @@ public class SimpleReport extends Abstra
</ul>
<p>To make sure everything went well and is properly declared, you can now
execute the below command in any other Maven project directory:</p>
-<div class="source"><pre class="prettyprint linenums"><code>$ mvn
com.mycompany.maven:simple-maven-plugin:1.0-SNAPSHOT:help
+<div class="source"><pre class="prettyprint linenums"><code
class="language-bash">$ mvn
com.mycompany.maven:simple-maven-plugin:1.0-SNAPSHOT:help
[INFO] --- simple-maven-plugin:1.0-SNAPSHOT:help (default-cli) @
hardware-connectors ---
[INFO] Simple Plugin 1.0-SNAPSHOT
@@ -472,7 +472,7 @@ simple:simple
<h4>Invoking the Simple Plugin</h4>
<p>To invoke the <em>report Mojo</em> of our plugin in another Maven project,
we just need to declare the plugin in the <a
href="/plugins/maven-site-plugin/examples/configuring-reports.html"><code><reporting></code></a>
section of its <code>pom.xml</code> as in the example below:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<reporting>
<plugins>
@@ -492,7 +492,7 @@ simple:simple
<p>In your <code>executeReport()</code> method, you will leverage the <a
href="/doxia/doxia/doxia-sink-api/">Doxia Sink API</a> to add elements to the
report document.</p>
<p>You will use the <a
href="/doxia/doxia/doxia-sink-api/apidocs/org/apache/maven/doxia/sink/Sink.html"><code>Sink</code></a>
object associated to the report:</p>
-<div class="source"><pre class="prettyprint linenums"><code>Sink sink =
getSink();
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">Sink sink = getSink();
</code></pre></div>
<p>This object allows you to append new elements to the report document
(initially empty). Unlike some DOM manipulation APIs, you cannot insert
elements in already existing elements, or remove elements.</p>
<p>The elements that you append to the document will look familiar if you have
basic knowledge of HTML. Most of the elements have opening and closing tags,
like <code>sink.body()</code> (opening) and <code>sink.body_()</code>
(closing).</p>
@@ -525,7 +525,7 @@ simple:simple
<h4>Creating more than one document</h4>
<p>You may need to create not just one HTML file, but several of them (like
Javadoc produces one HTML file for each Java class). To do so, you will need to
get a new <em>Sink</em> for each HTML file you need to produce. This is
achieved by using the <a
href="/doxia/doxia/doxia-sink-api/apidocs/org/apache/maven/doxia/sink/SinkFactory.html"><code>SinkFactory</code></a>
object that you can easily obtain with the <a
href="/shared/maven-reporting-impl/apidocs/org/apache/maven/reporting/AbstractMavenReport.html#getSinkFactory"><code>getSinkFactory()</code></a>
method of your <a
href="/shared/maven-reporting-impl/apidocs/org/apache/maven/reporting/AbstractMavenReport.html"><code>AbstractMavenReport</code></a>
instance, as in the example below.</p>
-<div class="source"><pre class="prettyprint linenums"><code>public class
SimpleReport extends AbstractMavenReport {
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">public class SimpleReport extends AbstractMavenReport {
...
Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
Modified: maven/website/content/plugin-developers/common-bugs.html
==============================================================================
--- maven/website/content/plugin-developers/common-bugs.html (original)
+++ maven/website/content/plugin-developers/common-bugs.html Sat Feb 18
18:17:30 2023
@@ -184,7 +184,7 @@ under the License.
<p>For example, if developer A has UTF-8 as default encoding while developer B
uses ISO-8859-1, text files are very likely to get messed up during resource
filtering or similar tasks.</p>
<p>Therefore, developers should avoid any direct or indirect usage of the
classes/methods that simply employ the platform's default encoding. For
instance, <code>FileWriter</code> and <code>FileReader</code> should usually be
avoided:</p>
-<div class="source"><pre class="prettyprint linenums"><code>/*
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">/*
* FIXME: This assumes the source file is using the platform's default
encoding.
*/
Reader reader = new FileReader( javaFile );
@@ -200,7 +200,7 @@ Reader reader = new FileReader( javaFile
</ul>
<p>Finally note that XML files require special handling because they are
equipped with an encoding declaration in the XML prolog. Reading or writing XML
files with an encoding that does not match their XML prolog's
<code>encoding</code> attribute is a bad idea:</p>
-<div class="source"><pre class="prettyprint linenums"><code>/*
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">/*
* FIXME: This assumes the XML encoding declaration matches the platform's
default encoding.
*/
Writer writer = new FileWriter( xmlFile );
@@ -210,7 +210,7 @@ writer.write( xmlContent );
<h3>Converting between URLs and Filesystem Paths</h3>
<p>URLs and filesystem paths are really two different things and converting
between them is not trivial. The main source of problems is that different
encoding rules apply for the strings that make up a URL or filesystem path. For
example, consider the following code snippet and its associated console
output:</p>
-<div class="source"><pre class="prettyprint linenums"><code>File file = new
File( "foo bar+foo" );
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">File file = new File( "foo bar+foo" );
URL url = file.toURI().toURL();
System.out.println( file.toURL() );
@@ -228,7 +228,7 @@ System.out.println( URLDecoder.decode( u
<p>First of all, please note that
<code>[File.toURL()](http://java.sun.com/javase/6/docs/api/java/io/File.html#toURL())</code>
does not escape the space character (and others). This yields an invalid URL,
as per <a href="http://www.faqs.org/rfcs/rfc2396.html"; class="externalLink">RFC
2396, section 2.4.3 “Excluded US-ASCII Characters”</a>. The class
<code>java.net.URL</code> will silently accept such invalid URLs, in contrast
<code>java.net.URI</code> will not (see also
<code>[URL.toURI()](http://java.sun.com/javase/6/docs/api/java/net/URL.html#toURI())</code>).
For this reason, <code>File.toURL()</code> has been deprecated and should be
replaced with <code>File.toURI().toURL()</code>.</p>
<p>Next,
<code>[URL.getPath()](http://java.sun.com/javase/6/docs/api/java/net/URL.html#getPath())</code>
does in general not return a string that can be used as a filesystem path. It
returns a substring of the URL and as such can contain escape sequences. The
prominent example is the space character which will show up as
“%20”. People sometimes hack around this by means of
<code>replace("%20", " ")</code> but that does simply not
cover all cases. It's worth to mention that on the other hand the related
method
<code>[URI.getPath()](http://java.sun.com/javase/6/docs/api/java/net/URI.html#getPath())</code>
does decode escapes but still the result is not a filesystem path (compare the
source for the constructor <code>File(URI)</code>). To summarize, the following
idiom is to be avoided:</p>
-<div class="source"><pre class="prettyprint linenums"><code>URL url = new URL(
"file:/C:/Program%20Files/Java/bin/java.exe" );
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">URL url = new URL(
"file:/C:/Program%20Files/Java/bin/java.exe" );
/*
* FIXME: This does not decode percent encoded characters.
@@ -238,7 +238,7 @@ File path = new File( url.getPath() );
<p>To decode a URL, people sometimes also choose
<code>[java.net.URLDecoder](http://java.sun.com/javase/6/docs/api/java/net/URLDecoder.html)</code>.
The pitfall with this class is that is actually performs HTML form decoding
which is yet another encoding and not the same as the URL encoding (compare the
last paragraph in class javadoc about
<code>[java.net.URL](http://java.sun.com/javase/6/docs/api/java/net/URL.html)</code>).
For instance, a <code>URLDecoder</code> will erroneously convert the character
“+” into a space as illustrated by the last sysout in the example
above.</p>
<p>In an ideal world, code targetting JRE 1.4+ could easily avoid these
problems by using the constructor
<code>[File(URI)](http://java.sun.com/javase/6/docs/api/java/io/File.html#File(java.net.URI))</code>
as suggested by the following snippet:</p>
-<div class="source"><pre class="prettyprint linenums"><code>URL url = new URL(
"file:/C:/Documents and Settings/user/.m2/settings.xml" );
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">URL url = new URL( "file:/C:/Documents and
Settings/user/.m2/settings.xml" );
/*
* FIXME: This assumes the URL is fully compliant with RFC 3986.
@@ -251,7 +251,7 @@ File path = new File( new URI( url.toExt
<p>When developers need to compare strings without regard to case or want to
realize a map with case-insensitive string keys, they often employ
<code>[String.toLowerCase()](http://java.sun.com/javase/6/docs/api/java/lang/String.html#toLowerCase())</code>
or
<code>[String.toUpperCase()](http://java.sun.com/javase/6/docs/api/java/lang/String.html#toUpperCase())</code>
to create a “normalized” string before doing a simple
<code>String.equals()</code>. Now, the <code>to\*Case()</code> methods are
overloaded: One takes no arguments and one takes a <code>Locale</code>
object.</p>
<p>The gotcha with the arg-less methods is that their output depends on the
default locale of the JVM but the default locale is out of control of the
developer. That means the string expected by the developer (who runs/tests his
code in a JVM using locale <code>xy</code>) does not necessarily match the
string seen by another user (that runs a JVM with locale <code>ab</code>). For
example, the comparison shown in the next code snippet is likely to fail for
systems with default locale Turkish because Turkish has unusual casing rules
for the characters “i” and “I”:</p>
-<div class="source"><pre class="prettyprint linenums"><code>/*
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">/*
* FIXME: This assumes the casing rules of the current platform
* match the rules for the English locale.
*/
@@ -276,7 +276,7 @@ if ( "info".equals( debugLevel
<h3>Using System Properties</h3>
<p>Maven's command line supports the definition of system properties via
arguments of the form <code>-D key=value</code>. While these properties are
called system properties, plugins should never use
<code>[System.getProperty()](http://java.sun.com/javase/6/docs/api/java/lang/System.html#getProperty(java.lang.String))</code>
and related methods to query these properties. For example, the following code
snippet will not work reliably when Maven is embedded, say into an IDE or a CI
server:</p>
-<div class="source"><pre class="prettyprint linenums"><code>public MyMojo
extends AbstractMojo
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">public MyMojo extends AbstractMojo
{
public void execute()
{
@@ -291,7 +291,7 @@ if ( "info".equals( debugLevel
<h3>Using Shutdown Hooks</h3>
<p>People occasionally employ shutdown hooks to perform cleanup tasks, e.g. to
delete temporary files as shown in the example below:</p>
-<div class="source"><pre class="prettyprint linenums"><code>public MyMojo
extends AbstractMojo
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">public MyMojo extends AbstractMojo
{
public void execute()
{
@@ -318,7 +318,7 @@ if ( "info".equals( debugLevel
<p>While it is surely an uncommon use-case, the user is free to invoke Maven
from an arbitrary working directory by specifying an absolute path like
<code>mvn -f /home/me/projects/demo/pom.xml</code>.</p>
<p>Hence this example code is prone to misbehave:</p>
-<div class="source"><pre class="prettyprint linenums"><code>public MyMojo
extends AbstractMojo
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">public MyMojo extends AbstractMojo
{
/**
* @parameter
@@ -337,7 +337,7 @@ if ( "info".equals( debugLevel
</code></pre></div>
<p>In order to guarantee reliable builds, Maven and its plugins must manually
resolve relative paths against the project's base directory. A simple idiom
like the following will do just fine:</p>
-<div class="source"><pre class="prettyprint linenums"><code>File file = new
File( path );
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">File file = new File( path );
if ( !file.isAbsolute() )
{
file = new File( project.getBasedir(), file );
@@ -348,7 +348,7 @@ if ( !file.isAbsolute() )
<p>Most reporting plugins inherit from <code>AbstractMavenReport</code>. In
doing so, they need to implement the inherited but abstract method
<code>getOutputDirectory()</code>. To implement this method, plugins usually
declare a field named <code>outputDirectory</code> which they return in the
method. Nothing wrong so far.</p>
<p>Now, some plugins need to create additional files in the report output
directory that accompany the report generated via the sink interface. While it
is tempting to use either the method <code>getOutputDirectory()</code> or the
field <code>outputDirectory</code> directly in order to setup a path for the
output files, this leads most likely to a bug. More precisely, those plugins
will not properly output files when run by the Maven Site Plugin as part of the
site lifecycle. This is best noticed when the output directory for the site is
configured directly in the Maven Site Plugin such that it deviates from the
expression <code>${project.reporting.outputDirectory}</code> that the plugins
use by default. Multi-language site generation is another scenario to exploit
this bug which is illustrated below:</p>
-<div class="source"><pre class="prettyprint linenums"><code>public
MyReportMojo extends AbstractMavenReport
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">public MyReportMojo extends AbstractMavenReport
{
/**
* @parameter
default-value="${project.reporting.outputDirectory}"
@@ -376,7 +376,7 @@ if ( !file.isAbsolute() )
<p>Maven employs an IoC container named Plexus to setup a plugin's mojos
before their execution. In other words, components required by a mojo will be
provided by means of dependency injection, more precisely field injection. The
important point to keep in mind is that this field injection happens
<em>after</em> the mojo's constructor has finished. This means that references
to injected components are invalid during the construction time of the mojo.</p>
<p>For example, the next snippet tries to retrieve the mojo logger during
construction time but the mojo logger is an injected component and as such has
not been properly initialized yet:</p>
-<div class="source"><pre class="prettyprint linenums"><code>public MyMojo
extends AbstractMojo
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">public MyMojo extends AbstractMojo
{
/*
* FIXME: This will retrieve a wrong logger instead of the intended mojo
logger.
Modified:
maven/website/content/plugin-developers/cookbook/plexus-plugin-upgrade.html
==============================================================================
--- maven/website/content/plugin-developers/cookbook/plexus-plugin-upgrade.html
(original)
+++ maven/website/content/plugin-developers/cookbook/plexus-plugin-upgrade.html
Sat Feb 18 18:17:30 2023
@@ -225,7 +225,7 @@ under the License.
<td>javadoc tags:  </td></tr>
<tr class="a">
<td><code>@plexus.component</code>, <code>@plexus.requirement</code>,
<code>@plexus.configuration</code>  </td>
-<td>javadoc tags + <a
href="https://codehaus-plexus.github.io/plexus-containers/plexus-component-annotations/";
class="externalLink"><code>plexus-component-annotations</code></a> Java 5
annotations: </td></tr>
+<td>javadoc tags + <a
href="https://codehaus-plexus.github.io/plexus-containers/plexus-component-annotations/";
class="externalLink"><code>plexus-component-annotations</code></a> Java 5
annotations:</td></tr>
<tr class="b">
<td><a
href="https://codehaus-plexus.github.io/plexus-containers/plexus-component-annotations/apidocs/org/codehaus/plexus/component/annotations/Component.html";
class="externalLink"><code>@Component</code></a>, <a
href="https://codehaus-plexus.github.io/plexus-containers/plexus-component-annotations/apidocs/org/codehaus/plexus/component/annotations/Requirement.html";
class="externalLink"><code>@Requirement</code></a>, <a
href="https://codehaus-plexus.github.io/plexus-containers/plexus-component-annotations/apidocs/org/codehaus/plexus/component/annotations/Configuration.html";
class="externalLink"><code>@Configuration</code></a>,</td></tr></tbody>
</table>
@@ -234,7 +234,7 @@ under the License.
<h4>Plugin Configuration</h4>
<p>In your <code>pom.xml</code>, replace <code>plexus-maven-plugin</code>
configuration:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
<build>
<plugins>
<plugin>
@@ -254,7 +254,7 @@ under the License.
</code></pre></div>
<p>with corresponding <code>plexus-component-metadata</code> configuration:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
<build>
<plugins>
<plugin>
@@ -276,7 +276,7 @@ under the License.
<h4>Replacing Plexus Javadoc Tags with Plexus Java 5 Annotations</h4>
<p>In your <code>pom.xml</code>, add <code>plexus-component-annotations</code>
dependency:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
<dependencies>
<dependency>
<groupId>org.codehaus.plexus</groupId>
@@ -288,7 +288,7 @@ under the License.
</code></pre></div>
<p>In your java sources, replace javadoc tags:</p>
-<div class="source"><pre class="prettyprint linenums"><code>/**
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">/**
* @plexus.component role="foo.MyComponent"
role-hint="hint-value"
*/
public class MyComponentImplementation
@@ -302,7 +302,7 @@ public class MyComponentImplementation
</code></pre></div>
<p>with corresponding Java 5 annotations</p>
-<div class="source"><pre class="prettyprint linenums"><code>import
org.codehaus.plexus.component.annotations.Component;
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">import
org.codehaus.plexus.component.annotations.Component;
import org.codehaus.plexus.component.annotations.Requirement;
@Component( role = MyComponent.class, hint = "hint-value" )
Modified: maven/website/content/plugin-developers/plugin-testing.html
==============================================================================
--- maven/website/content/plugin-developers/plugin-testing.html (original)
+++ maven/website/content/plugin-developers/plugin-testing.html Sat Feb 18
18:17:30 2023
@@ -174,7 +174,7 @@ under the License.
<p>The <a
href="/plugin-testing/maven-plugin-testing-harness/">maven-plugin-testing-harness</a>
is explicitly intended to test the
<code>org.apache.maven.reporting.AbstractMavenReport#execute()</code>
implementation.</p>
<p>In general, you need to include <code>maven-plugin-testing-harness</code>
as a dependency, and create a *MojoTest (by convention) class which
<code>extends AbstractMojoTestCase</code>.</p>
-<div class="source"><pre class="prettyprint linenums"><code>...
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml">...
<dependencies>
...
<dependency>
@@ -188,7 +188,7 @@ under the License.
...
</code></pre></div>
-<div class="source"><pre class="prettyprint linenums"><code>public class
YourMojoTest
+<div class="source"><pre class="prettyprint linenums"><code
class="language-java">public class YourMojoTest
extends AbstractMojoTestCase
{
/**
@@ -224,7 +224,7 @@ under the License.
<p>You can use <a
href="https://maven.apache.org/plugins/maven-invoker-plugin/";
class="externalLink">maven-invoker-plugin</a> to invoke Maven and to provide
some BeanShell/Groovy tests. Tests written in this way don't run under
JUnit/TestNG; instead, they're run by Maven itself.</p>
<p>You can take a look at the <a
href="https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-install-plugin/src/it/";
class="externalLink">maven-install-plugin</a> how there are integration tests
are written.</p>
-<div class="source"><pre class="prettyprint linenums"><code><project
xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+<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">
...
<build>
Modified: maven/website/content/plugins/localization.html
==============================================================================
--- maven/website/content/plugins/localization.html (original)
+++ maven/website/content/plugins/localization.html Sat Feb 18 18:17:30 2023
@@ -549,7 +549,7 @@ under the License.
<p>Configure a project to use the latest SNAPSHOT version of the plugin you
are working on. Also configure the project to produce a site in the language
you are adding a translation for. For Spanish, as we used in the example above,
it would look like this:</p></li>
</ul>
-<div class="source"><pre class="prettyprint linenums"><code> <build>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"> <build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
Modified: maven/website/content/repository/central-index.html
==============================================================================
--- maven/website/content/repository/central-index.html (original)
+++ maven/website/content/repository/central-index.html Sat Feb 18 18:17:30 2023
@@ -177,7 +177,7 @@ under the License.
<li>download and extract <a
href="https://github.com/DmitryKey/luke/releases/download/luke-4.10.4/luke-with-deps.tar.gz";
class="externalLink">Luke binary tarball</a> and launch it on the Central
index with Lucene format:</li>
</ul>
-<div class="source"><pre class="prettyprint linenums"><code>luke.sh -ro -index
central-lucene-index
+<div class="source"><pre class="prettyprint linenums"><code
class="language-bash">luke.sh -ro -index central-lucene-index
</code></pre></div>
<p>You need an old Luke version using an old Lucene version, since Maven
Indexer 5.5.1 uses Lucene 3.6.2: for this tutorial, we chose Luke version
4.10.4, but you may choose another version.</p></section></section></section>
</main>
Modified: maven/website/content/repository/guide-central-repository-upload.html
==============================================================================
--- maven/website/content/repository/guide-central-repository-upload.html
(original)
+++ maven/website/content/repository/guide-central-repository-upload.html Sat
Feb 18 18:17:30 2023
@@ -170,9 +170,9 @@ under the License.
<p>Some folks have asked <em>“why do we require all this information in
the POM for deployed artifacts?”</em>, so here's a small explanation.</p>
<p>The POM being deployed with the artifact is part of the process to make
transitive dependencies a reality in Maven. The logic for getting transitive
dependencies working is really not that hard, the problem is getting the data.
The other applications that are made possible by having all the POMs available
for artifacts are vast, so by placing them into the Central Repository as part
of the process we open up the doors to new ideas that involve unified access to
project POMs.</p>
<p>We ask for the license because it is possible that your project's license
may change in the course of its lifetime, and we are trying to create tools to
help sort out licensing issues. For example, knowing all the licenses for a
particular graph of artifacts, we could have some strategies that would
identify potential licensing problems.</p></section><section>
-<h3>A basic sample:</h3>
+<h3>A basic sample</h3>
-<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>
<groupId>org.apache.maven</groupId>
Modified: maven/website/content/security-plexus-archiver.html
==============================================================================
--- maven/website/content/security-plexus-archiver.html (original)
+++ maven/website/content/security-plexus-archiver.html Sat Feb 18 18:17:30 2023
@@ -200,7 +200,7 @@ which versions contain the fixed and the
<td>maven-ear-plugin</td>
-<td>(,3.0.0]</td>
+<td>(,3.0.0]</td>
<td>3.0.1</td>
@@ -276,7 +276,7 @@ which versions contain the fixed and the
<td></td>
<td><a href="https://issues.apache.org/jira/browse/MANTRUN-214";
class="externalLink">MANTRUN-214</a></td>
-
+
<td></td>
</tr>
@@ -289,7 +289,7 @@ which versions contain the fixed and the
<td></td>
<td><a href="https://issues.apache.org/jira/browse/MPLUGIN-340";
class="externalLink">MPLUGIN-340</a></td>
-
+
<td><a href="/plugin-tools/maven-plugin-plugin/examples/ant-mojo.html">Ant
Mojo Wrapper</a></td>
</tr>
</table>
Modified: maven/website/content/skins/index.html
==============================================================================
--- maven/website/content/skins/index.html (original)
+++ maven/website/content/skins/index.html Sat Feb 18 18:17:30 2023
@@ -215,7 +215,7 @@ under the License.
<td><a href="https://github.com/devacfr"; class="externalLink">Friederich
Christophe</a></td>
<td>Responsive 2 Apache Maven skin to reflow the standard Maven site with a
modern feel.</td></tr>
<tr class="b">
-<td><a href="http://docs.bernardomg.com/maven/docs-maven-skin/";
class="externalLink"><code>Docs Maven Skin</code></a></td>
+<td><a href="http://docs.bernardomg.com/maven/docs-maven-skin/";
class="externalLink">Bernardo Martínez Garrido</a></td>
<td><a href="https://github.com/Bernardo-MG"; class="externalLink">Bernardo
Martínez Garrido</a></td>
<td>A minimalist and responsive Bootstrap-based HTML5 skin for Maven Site,
which will help to use it as a documentation site.</td></tr>
<tr class="a">
@@ -227,7 +227,7 @@ under the License.
<h3>Instructions</h3>
<p>To use one of these skins in your project, you use the <code>skin</code>
element of the <a
href="/plugins/maven-site-plugin/examples/sitedescriptor.html">site
descriptor</a>. This is a regular artifact or dependency-like element. For
example, to use the Maven Fluido Skin, you would include the this in your
<code>site.xml</code> file:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code
class="language-xml"><project>
...
<skin>
<groupId>org.apache.maven.skins</groupId>
