This is an automated email from the ASF dual-hosted git repository.
elharo pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git
The following commit(s) were added to refs/heads/master by this push:
new ecf9fffa add namespace to examples (#1350)
ecf9fffa is described below
commit ecf9fffa11e4084d4bf46c482e589791fde9fee7
Author: Elliotte Rusty Harold <elh...@users.noreply.github.com>
AuthorDate: Fri Jul 25 11:36:27 2025 -0400
add namespace to examples (#1350)
---
.../examples/injecting-properties-via-settings.apt | 2 +-
.../development/guide-documentation-style.apt | 2 +-
.../guide-testing-development-plugins.apt | 4 +--
.../introduction-to-dependency-mechanism.apt | 26 +++++++++---------
...ction-to-optional-and-excludes-dependencies.apt | 8 +++---
.../introduction/introduction-to-profiles.apt | 8 +++---
.../introduction/introduction-to-repositories.apt | 2 +-
.../introduction/introduction-to-the-pom.apt | 30 ++++++++++----------
.../guides/mini/guide-archive-configuration.apt | 2 +-
content/apt/guides/mini/guide-assemblies.apt | 2 +-
content/apt/guides/mini/guide-attached-tests.apt | 4 +--
.../apt/guides/mini/guide-configuring-plugins.apt | 32 +++++++++++-----------
.../apt/guides/mini/guide-generating-sources.apt | 2 +-
.../guides/mini/guide-multiple-repositories.apt | 2 +-
content/apt/guides/mini/guide-releasing.apt | 6 ++--
content/apt/guides/mini/guide-relocation.apt | 2 +-
content/apt/guides/mini/guide-site.apt | 6 ++--
content/apt/guides/mini/guide-using-ant.apt | 4 +--
content/apt/guides/mini/guide-using-extensions.apt | 4 +--
content/apt/guides/mini/guide-using-modello.apt | 2 +-
.../mini/guide-using-one-source-directory.apt | 4 +--
.../cookbook/plexus-plugin-upgrade.apt | 6 ++--
.../repository/guide-central-repository-upload.apt | 2 +-
23 files changed, 81 insertions(+), 81 deletions(-)
diff --git a/content/apt/examples/injecting-properties-via-settings.apt
b/content/apt/examples/injecting-properties-via-settings.apt
index 09498baa..c637b2b6 100644
--- a/content/apt/examples/injecting-properties-via-settings.apt
+++ b/content/apt/examples/injecting-properties-via-settings.apt
@@ -37,7 +37,7 @@ Example: Injecting POM Properties via Settings.xml
* Plugin Configuration
+---+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
[...]
<build>
<plugins>
diff --git a/content/apt/guides/development/guide-documentation-style.apt
b/content/apt/guides/development/guide-documentation-style.apt
index 09817584..5fe8fd68 100644
--- a/content/apt/guides/development/guide-documentation-style.apt
+++ b/content/apt/guides/development/guide-documentation-style.apt
@@ -98,7 +98,7 @@ Guide To Maven Documentation Style
site is configured.
+-----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<distributionManagement>
<site>
diff --git
a/content/apt/guides/development/guide-testing-development-plugins.apt
b/content/apt/guides/development/guide-testing-development-plugins.apt
index 32de8b42..aeb65c4d 100644
--- a/content/apt/guides/development/guide-testing-development-plugins.apt
+++ b/content/apt/guides/development/guide-testing-development-plugins.apt
@@ -50,7 +50,7 @@ Guide to Testing Development Versions of Plugins
The first step is to include this in your project:
+-------
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<pluginRepositories>
<pluginRepository>
@@ -71,7 +71,7 @@ Guide to Testing Development Versions of Plugins
* You can have Maven automatically check for updates on a given interval,
for example:
+-------
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<pluginRepositories>
<pluginRepository>
diff --git
a/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
b/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
index a5e2285a..cc8e263a 100644
--- a/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
+++ b/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
@@ -207,7 +207,7 @@ Introduction to the Dependency Mechanism
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<dependencies>
<dependency>
@@ -237,7 +237,7 @@ Introduction to the Dependency Mechanism
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<dependencies>
<dependency>
@@ -264,7 +264,7 @@ Introduction to the Dependency Mechanism
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<dependencyManagement>
<dependencies>
@@ -307,7 +307,7 @@ Introduction to the Dependency Mechanism
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<dependencies>
<dependency>
@@ -328,7 +328,7 @@ Introduction to the Dependency Mechanism
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<dependencies>
<dependency>
@@ -364,7 +364,7 @@ Introduction to the Dependency Mechanism
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>maven</groupId>
<artifactId>A</artifactId>
@@ -405,7 +405,7 @@ Introduction to the Dependency Mechanism
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<parent>
<artifactId>A</artifactId>
<groupId>maven</groupId>
@@ -479,7 +479,7 @@ Introduction to the Dependency Mechanism
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>maven</groupId>
<artifactId>B</artifactId>
@@ -528,7 +528,7 @@ Introduction to the Dependency Mechanism
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>maven</groupId>
<artifactId>X</artifactId>
@@ -559,7 +559,7 @@ Introduction to the Dependency Mechanism
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>maven</groupId>
<artifactId>Y</artifactId>
@@ -590,7 +590,7 @@ Introduction to the Dependency Mechanism
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>maven</groupId>
<artifactId>Z</artifactId>
@@ -871,7 +871,7 @@ Introduction to the Dependency Mechanism
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<dependencies>
<dependency>
@@ -891,7 +891,7 @@ Introduction to the Dependency Mechanism
would be defined as follows:
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<dependencies>
<dependency>
diff --git
a/content/apt/guides/introduction/introduction-to-optional-and-excludes-dependencies.apt
b/content/apt/guides/introduction/introduction-to-optional-and-excludes-dependencies.apt
index 4ecceba6..01dbcf34 100644
---
a/content/apt/guides/introduction/introduction-to-optional-and-excludes-dependencies.apt
+++
b/content/apt/guides/introduction/introduction-to-optional-and-excludes-dependencies.apt
@@ -64,7 +64,7 @@ Introduction
+---+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<dependencies>
<!-- declare the dependency to be set as optional -->
@@ -138,7 +138,7 @@ Project-X -> Project-A
+---+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<dependencies>
<dependency>
@@ -200,7 +200,7 @@ B, C, D, E, F
+---+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>sample.ProjectA</groupId>
<artifactId>Project-A</artifactId>
@@ -280,7 +280,7 @@ Project-A
+---+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>sample.ProjectA</groupId>
<artifactId>Project-A</artifactId>
diff --git a/content/apt/guides/introduction/introduction-to-profiles.apt
b/content/apt/guides/introduction/introduction-to-profiles.apt
index cddb1405..ef0d145e 100644
--- a/content/apt/guides/introduction/introduction-to-profiles.apt
+++ b/content/apt/guides/introduction/introduction-to-profiles.apt
@@ -512,7 +512,7 @@ mvn groupId:artifactId:goal
-P=-profile-1,-profile-2,-?profile-3
Example:
+---+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<repositories>
<repository>
@@ -580,7 +580,7 @@ mvn groupId:artifactId:goal
-P=-profile-1,-profile-2,-?profile-3
Consider the following <<<pom.xml>>> snippet for a web application project:
+---+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<build>
<plugins>
@@ -649,7 +649,7 @@ mvn groupId:artifactId:goal
-P=-profile-1,-profile-2,-?profile-3
snippet from above one more time:
+---+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<build>
<plugins>
@@ -672,7 +672,7 @@ mvn groupId:artifactId:goal
-P=-profile-1,-profile-2,-?profile-3
<<<pom.xml>>>:
+---+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<profiles>
<profile>
diff --git a/content/apt/guides/introduction/introduction-to-repositories.apt
b/content/apt/guides/introduction/introduction-to-repositories.apt
index 966ee557..da2c50eb 100644
--- a/content/apt/guides/introduction/introduction-to-repositories.apt
+++ b/content/apt/guides/introduction/introduction-to-repositories.apt
@@ -136,7 +136,7 @@ Introduction to Repositories
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<repositories>
<repository>
diff --git a/content/apt/guides/introduction/introduction-to-the-pom.apt
b/content/apt/guides/introduction/introduction-to-the-pom.apt
index 62027e54..753f1fc0 100644
--- a/content/apt/guides/introduction/introduction-to-the-pom.apt
+++ b/content/apt/guides/introduction/introduction-to-the-pom.apt
@@ -75,7 +75,7 @@ Introduction to the POM
Here's an example:
+-----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
@@ -130,7 +130,7 @@ Introduction to the POM
com.mycompany.app:my-module:1.
+-----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
@@ -159,7 +159,7 @@ Introduction to the POM
<<com.mycompany.app:my-module:1's POM>>
+-----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<parent>
@@ -182,7 +182,7 @@ Introduction to the POM
remove the groupId or the version identity of your module in its POM.
+-----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<parent>
@@ -222,7 +222,7 @@ Introduction to the POM
our parent section.
+-----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<parent>
@@ -262,7 +262,7 @@ Introduction to the POM
<<com.mycompany.app:my-app:1's POM>>
+-----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
@@ -274,7 +274,7 @@ Introduction to the POM
<<com.mycompany.app:my-module:1's POM>>
+-----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
@@ -297,7 +297,7 @@ Introduction to the POM
If we are to aggregate my-module into my-app, we would only have to modify
my-app.
+-----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
@@ -343,7 +343,7 @@ Introduction to the POM
The answer? - the same way as Example 3, by specifying the path to the module.
+-----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
@@ -390,7 +390,7 @@ Introduction to the POM
<<com.mycompany.app:my-app:1's POM>>
+-----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
@@ -402,7 +402,7 @@ Introduction to the POM
<<com.mycompany.app:my-module:1's POM>>
+-----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
@@ -428,7 +428,7 @@ Introduction to the POM
<<com.mycompany.app:my-app:1's POM>>
+-----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
@@ -445,7 +445,7 @@ Introduction to the POM
<<com.mycompany.app:my-module:1's POM>>
+-----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<parent>
@@ -499,7 +499,7 @@ Introduction to the POM
shown in the example below:
+----+
-<project>
+<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>
@@ -517,7 +517,7 @@ Introduction to the POM
You are also able to reference any properties defined in the project as a
variable. Consider the following example:
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<properties>
<mavenVersion>3.0</mavenVersion>
diff --git a/content/apt/guides/mini/guide-archive-configuration.apt
b/content/apt/guides/mini/guide-archive-configuration.apt
index 6e532783..4028fa9b 100644
--- a/content/apt/guides/mini/guide-archive-configuration.apt
+++ b/content/apt/guides/mini/guide-archive-configuration.apt
@@ -40,7 +40,7 @@ Guide to Configuring Archive Plugins
is used):
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<build>
<plugins>
diff --git a/content/apt/guides/mini/guide-assemblies.apt
b/content/apt/guides/mini/guide-assemblies.apt
index f35ba587..5fd264a5 100644
--- a/content/apt/guides/mini/guide-assemblies.apt
+++ b/content/apt/guides/mini/guide-assemblies.apt
@@ -33,7 +33,7 @@ Guide to creating assemblies
assembly plug-in in your POM and it might look like the following:
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<parent>
<artifactId>maven</artifactId>
<groupId>org.apache.maven</groupId>
diff --git a/content/apt/guides/mini/guide-attached-tests.apt
b/content/apt/guides/mini/guide-attached-tests.apt
index 5af57d48..c8891e8a 100644
--- a/content/apt/guides/mini/guide-attached-tests.apt
+++ b/content/apt/guides/mini/guide-attached-tests.apt
@@ -35,7 +35,7 @@ Guide to using attached tests
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<build>
<plugins>
<plugin>
@@ -63,7 +63,7 @@ Guide to using attached tests
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<dependencies>
<dependency>
diff --git a/content/apt/guides/mini/guide-configuring-plugins.apt
b/content/apt/guides/mini/guide-configuring-plugins.apt
index 081ea49c..71b65840 100644
--- a/content/apt/guides/mini/guide-configuring-plugins.apt
+++ b/content/apt/guides/mini/guide-configuring-plugins.apt
@@ -91,7 +91,7 @@ public class MyQueryMojo
the following:
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<build>
<plugins>
@@ -159,7 +159,7 @@ mvn javadoc:help -Ddetail -Dgoal=javadoc
the following:
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<configuration>
<myString>a string</myString>
@@ -221,7 +221,7 @@ mvn javadoc:help -Ddetail -Dgoal=javadoc
following:
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<configuration>
<person>
@@ -250,7 +250,7 @@ mvn javadoc:help -Ddetail -Dgoal=javadoc
[]
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<configuration>
<person implementation="com.mycompany.mojo.query.SuperPerson">
@@ -290,7 +290,7 @@ public class MyAnimalMojo
where you have a field named <<<animals>>> then your configuration for the
plug-in would look like the following:
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<build>
<plugins>
@@ -346,7 +346,7 @@ public class MyAnimalMojo
The following example is equivalent to the example above:
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<build>
<plugins>
@@ -378,7 +378,7 @@ public class MyAnimalMojo
+-----+
+-----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<configuration>
<myMap>
@@ -412,7 +412,7 @@ public class MyAnimalMojo
+-----+
+-----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<configuration>
<myProperties>
@@ -443,7 +443,7 @@ public class MyAnimalMojo
Using <<<MyQueryMojo>>> as an example, you may have something that will look
like:
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<build>
<plugins>
@@ -507,7 +507,7 @@ public class MyAnimalMojo
this time we shall bind <<<execution2>>> to a phase.
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<build>
<plugins>
@@ -556,7 +556,7 @@ public class MyAnimalMojo
Using the following definition would execute <<<execution2>>> before
<<<execution1>>>, but both in the test phase.
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<build>
<plugins>
@@ -611,7 +611,7 @@ public class MyBoundQueryMojo
using the <<<\<phase\>>>> tag under <<<\<execution\>>>>.
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<build>
<plugins>
@@ -669,7 +669,7 @@ mvn myquery:query@execution1
when running this plugin, you need to add <<<\<dependencies\>>>> element
like the following:
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<build>
<plugins>
@@ -703,7 +703,7 @@ mvn myquery:query@execution1
the <<<\<inherited\>>>> tag:
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<build>
<plugins>
@@ -745,7 +745,7 @@ mvn myquery:query@execution1
reports selectively when running <<<mvn site>>>. The following will generate
only the project team report.
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<reporting>
<plugins>
@@ -788,7 +788,7 @@ mvn myquery:query@execution1
Similar to the build plugins, to break the inheritance, you can use the
<<<\<inherited\>>>> tag:
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<reporting>
<plugins>
diff --git a/content/apt/guides/mini/guide-generating-sources.apt
b/content/apt/guides/mini/guide-generating-sources.apt
index f98d5319..61a8e2e2 100644
--- a/content/apt/guides/mini/guide-generating-sources.apt
+++ b/content/apt/guides/mini/guide-generating-sources.apt
@@ -37,7 +37,7 @@ Guide to generating sources
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<build>
<plugins>
diff --git a/content/apt/guides/mini/guide-multiple-repositories.apt
b/content/apt/guides/mini/guide-multiple-repositories.apt
index 4ab83eb8..0193e28c 100644
--- a/content/apt/guides/mini/guide-multiple-repositories.apt
+++ b/content/apt/guides/mini/guide-multiple-repositories.apt
@@ -33,7 +33,7 @@ Setting up Multiple Repositories
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<repositories>
<repository>
diff --git a/content/apt/guides/mini/guide-releasing.apt
b/content/apt/guides/mini/guide-releasing.apt
index 04bd5287..8cf06eaf 100644
--- a/content/apt/guides/mini/guide-releasing.apt
+++ b/content/apt/guides/mini/guide-releasing.apt
@@ -92,7 +92,7 @@ mvn release:prepare \
within the <pom.xml> file in the following form:
+-----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
<artifactId>app</artifactId>
@@ -130,7 +130,7 @@ mvn release:prepare \
The following example shows how this would look within the <pom.xml> file.
+-----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
<artifactId>app</artifactId>
@@ -246,7 +246,7 @@ checkpoint.check-in-development-version=OK
The following is an example of how a distributionManagement element can be
configured within a project <pom.xml> file.
+-----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
<artifactId>app</artifactId>
diff --git a/content/apt/guides/mini/guide-relocation.apt
b/content/apt/guides/mini/guide-relocation.apt
index 0a64fa82..7f27e2b6 100644
--- a/content/apt/guides/mini/guide-relocation.apt
+++ b/content/apt/guides/mini/guide-relocation.apt
@@ -64,7 +64,7 @@ Guide to relocation
The minimal POM file might look like this for version 1.0 of <<<foo>>>:
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>bar</groupId>
<artifactId>foo</artifactId>
diff --git a/content/apt/guides/mini/guide-site.apt
b/content/apt/guides/mini/guide-site.apt
index 85e713a2..57937e4f 100644
--- a/content/apt/guides/mini/guide-site.apt
+++ b/content/apt/guides/mini/guide-site.apt
@@ -108,7 +108,7 @@ mvn site
similar to the repository for deployment:
+--------------
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<distributionManagement>
<site>
@@ -268,7 +268,7 @@ mvn site-deploy
POM in a friendly format:
+------------------
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<reporting>
<plugins>
@@ -307,7 +307,7 @@ mvn site-deploy
To enable multiple locales, add a configuration similar to the following to
your POM:
+------------------
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<build>
<plugins>
diff --git a/content/apt/guides/mini/guide-using-ant.apt
b/content/apt/guides/mini/guide-using-ant.apt
index d75d359b..ea317f24 100644
--- a/content/apt/guides/mini/guide-using-ant.apt
+++ b/content/apt/guides/mini/guide-using-ant.apt
@@ -33,7 +33,7 @@ Guide to using Ant with Maven
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<artifactId>my-test-app</artifactId>
<groupId>my-test-group</groupId>
@@ -73,7 +73,7 @@ Guide to using Ant with Maven
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<artifactId>my-test-app</artifactId>
<groupId>my-test-group</groupId>
diff --git a/content/apt/guides/mini/guide-using-extensions.apt
b/content/apt/guides/mini/guide-using-extensions.apt
index 79b847cb..4668c9bc 100644
--- a/content/apt/guides/mini/guide-using-extensions.apt
+++ b/content/apt/guides/mini/guide-using-extensions.apt
@@ -65,7 +65,7 @@ Using Extensions
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<build>
<plugins>
@@ -90,7 +90,7 @@ Using Extensions
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<build>
<extensions>
diff --git a/content/apt/guides/mini/guide-using-modello.apt
b/content/apt/guides/mini/guide-using-modello.apt
index 0e4b31ec..68cb83ce 100644
--- a/content/apt/guides/mini/guide-using-modello.apt
+++ b/content/apt/guides/mini/guide-using-modello.apt
@@ -54,7 +54,7 @@ Guide to using Modello
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
...
<build>
<plugins>
diff --git a/content/apt/guides/mini/guide-using-one-source-directory.apt
b/content/apt/guides/mini/guide-using-one-source-directory.apt
index ffacd8fb..91f9bdd0 100644
--- a/content/apt/guides/mini/guide-using-one-source-directory.apt
+++ b/content/apt/guides/mini/guide-using-one-source-directory.apt
@@ -109,7 +109,7 @@ Using Maven When You Can't Use the Conventions
First, you set up your <<<pom.xml>>> at the top level not to produce
anything, but to include the other modules we plan to create:
+--------
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<artifactId>my-parent</artifactId>
<packaging>pom</packaging>
...
@@ -124,7 +124,7 @@ Using Maven When You Can't Use the Conventions
<<<module>>> subdirectory will be similar.
+--------
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>my-groupId</groupId>
diff --git a/content/apt/plugin-developers/cookbook/plexus-plugin-upgrade.apt
b/content/apt/plugin-developers/cookbook/plexus-plugin-upgrade.apt
index 5820526d..f75f8a79 100644
--- a/content/apt/plugin-developers/cookbook/plexus-plugin-upgrade.apt
+++ b/content/apt/plugin-developers/cookbook/plexus-plugin-upgrade.apt
@@ -98,7 +98,7 @@ Cookbook: How To Upgrade from Plexus Javadoc Tags to Plexus
Java Annotations?
In your <<<pom.xml>>>, replace <<<plexus-maven-plugin>>> configuration:
+---------+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<build>
<plugins>
<plugin>
@@ -120,7 +120,7 @@ Cookbook: How To Upgrade from Plexus Javadoc Tags to Plexus
Java Annotations?
with corresponding <<<plexus-component-metadata>>> configuration:
+---------+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<build>
<plugins>
<plugin>
@@ -146,7 +146,7 @@ Cookbook: How To Upgrade from Plexus Javadoc Tags to Plexus
Java Annotations?
In your <<<pom.xml>>>, add <<<plexus-component-annotations>>> dependency:
+---------+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<dependencies>
<dependency>
<groupId>org.codehaus.plexus</groupId>
diff --git a/content/apt/repository/guide-central-repository-upload.apt
b/content/apt/repository/guide-central-repository-upload.apt
index f9764966..47b5d94f 100644
--- a/content/apt/repository/guide-central-repository-upload.apt
+++ b/content/apt/repository/guide-central-repository-upload.apt
@@ -60,7 +60,7 @@ Requirements
+----+
-<project>
+<project xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>org.apache.maven</groupId>
<artifactId>maven</artifactId>
