You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by el...@apache.org on 2025/08/10 14:27:18 UTC
(maven-site) branch rev created (now 3947e67d)
This is an automated email from the ASF dual-hosted git repository.
elharo pushed a change to branch rev
in repository https://gitbox.apache.org/repos/asf/maven-site.git
at 3947e67d Revert unreviewed commit
This branch includes the following new commits:
new 3947e67d Revert unreviewed commit
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
(maven-site) 01/01: Revert unreviewed commit
Posted by el...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
elharo pushed a commit to branch rev
in repository https://gitbox.apache.org/repos/asf/maven-site.git
commit 3947e67d782220354f0e60c0da36e9838ef68c41
Author: Elliotte Rusty Harold <el...@ibiblio.org>
AuthorDate: Sun Aug 10 15:26:52 2025 +0100
Revert unreviewed commit
---
content/markdown/guides/mini/guide-3rd-party-jars-local.md | 1 -
content/markdown/guides/mini/guide-3rd-party-jars-remote.md | 1 -
content/markdown/guides/mini/guide-archive-configuration.md | 1 -
content/markdown/guides/mini/guide-assemblies.md | 2 --
content/markdown/guides/mini/guide-attached-tests.md | 5 -----
content/markdown/guides/mini/guide-bash-m2-completion.md | 1 -
.../mini/guide-building-for-different-environments.md | 3 ---
content/markdown/guides/mini/guide-configuring-maven.md | 1 -
content/markdown/guides/mini/guide-configuring-plugins.md | 4 +---
content/markdown/guides/mini/guide-creating-archetypes.md | 13 -------------
content/markdown/guides/mini/guide-default-execution-ids.md | 1 -
.../guides/mini/guide-deployment-security-settings.md | 3 ---
content/markdown/guides/mini/guide-encryption.md | 1 -
content/markdown/guides/mini/guide-generating-sources.md | 3 ---
content/markdown/guides/mini/guide-http-settings.md | 2 --
.../mini/guide-large-scale-centralized-deployments.md | 1 -
content/markdown/guides/mini/guide-maven-ci-friendly.md | 10 ----------
content/markdown/guides/mini/guide-maven-classloading.md | 1 -
content/markdown/guides/mini/guide-migration-to-mvn4.md | 1 -
content/markdown/guides/mini/guide-multiple-modules.md | 1 -
content/markdown/guides/mini/guide-multiple-repositories.md | 7 -------
.../markdown/guides/mini/guide-multiple-subprojects-4.md | 1 -
content/markdown/guides/mini/guide-naming-conventions.md | 1 -
content/markdown/guides/mini/guide-new-committers.md | 1 -
content/markdown/guides/mini/guide-proxies.md | 3 ---
content/markdown/guides/mini/guide-releasing.md | 1 -
content/markdown/guides/mini/guide-relocation.md | 2 --
content/markdown/guides/mini/guide-repository-ssl.md | 1 -
content/markdown/guides/mini/guide-reproducible-builds.md | 1 -
content/markdown/guides/mini/guide-site.md | 1 -
content/markdown/guides/mini/guide-snippet-macro.md | 1 -
content/markdown/guides/mini/guide-using-ant.md | 5 -----
content/markdown/guides/mini/guide-using-extensions.md | 6 ------
content/markdown/guides/mini/guide-using-modello.md | 3 ---
.../guides/mini/guide-using-one-source-directory.md | 1 -
content/markdown/guides/mini/guide-using-toolchains.md | 1 -
content/markdown/guides/mini/guide-wagon-providers.md | 1 -
37 files changed, 1 insertion(+), 92 deletions(-)
diff --git a/content/markdown/guides/mini/guide-3rd-party-jars-local.md b/content/markdown/guides/mini/guide-3rd-party-jars-local.md
index 247adb01..e4b756c9 100644
--- a/content/markdown/guides/mini/guide-3rd-party-jars-local.md
+++ b/content/markdown/guides/mini/guide-3rd-party-jars-local.md
@@ -40,4 +40,3 @@ With version 2.5 of the maven-install-plugin, it can get even simpler: if the JA
```
mvn org.apache.maven.plugins:maven-install-plugin:2.5.2:install-file -Dfile=<path-to-file>
```
-
diff --git a/content/markdown/guides/mini/guide-3rd-party-jars-remote.md b/content/markdown/guides/mini/guide-3rd-party-jars-remote.md
index 8b11fdec..d86f8458 100644
--- a/content/markdown/guides/mini/guide-3rd-party-jars-remote.md
+++ b/content/markdown/guides/mini/guide-3rd-party-jars-remote.md
@@ -64,4 +64,3 @@ Note that `groupId`, `artifactId`, `version` and `packaging` arguments are not i
<!-- and the classifier should be set to source.-->
To deploy a 3rd party source jar, packaging should be set to `java-source`, and generatePom should be set to `false`.
-
diff --git a/content/markdown/guides/mini/guide-archive-configuration.md b/content/markdown/guides/mini/guide-archive-configuration.md
index 56054c3e..16d2fcf2 100644
--- a/content/markdown/guides/mini/guide-archive-configuration.md
+++ b/content/markdown/guides/mini/guide-archive-configuration.md
@@ -46,7 +46,6 @@ To disable the generation of these files, include the following configuration fo
</build>
...
</project>
-
```
<!-- other things: index, compress-->
diff --git a/content/markdown/guides/mini/guide-assemblies.md b/content/markdown/guides/mini/guide-assemblies.md
index 139ce358..eda083c5 100644
--- a/content/markdown/guides/mini/guide-assemblies.md
+++ b/content/markdown/guides/mini/guide-assemblies.md
@@ -138,7 +138,6 @@ How to use such pre-defined assembly descriptors is described in the [documentat
</dependencySet>
</dependencySets>
</assembly>
-
```
If you like to create a source distribution package the best solution is to use the [pre-defined assembly descriptor src](/plugins/maven-assembly-plugin/descriptor-refs.html#src) for such purposes.
@@ -176,4 +175,3 @@ You can now create the defined distribution packages via command line like this:
```
mvn package
```
-
diff --git a/content/markdown/guides/mini/guide-attached-tests.md b/content/markdown/guides/mini/guide-attached-tests.md
index 2a45ba58..2f28a2af 100644
--- a/content/markdown/guides/mini/guide-attached-tests.md
+++ b/content/markdown/guides/mini/guide-attached-tests.md
@@ -22,7 +22,6 @@ under the License.
You can reuse the tests that you have created for one project in another. For example, suppose `foo-core` contains test code in the `${project.basedir}/src/test/java`. To package up those compiled tests in a JAR and deploy them for general reuse, configure the `maven-jar-plugin` as follows:
```xml
-
<project xmlns="http://maven.apache.org/POM/4.0.0">
<build>
<plugins>
@@ -41,7 +40,6 @@ You can reuse the tests that you have created for one project in another. For ex
</plugins>
</build>
</project>
-
```
The attached test JAR can be installed and deployed like any other Maven artifact.
@@ -49,7 +47,6 @@ The attached test JAR can be installed and deployed like any other Maven artifac
To use the attached test JAR, specify a dependency on the main artifact with a specified type of `test-jar` and the `classifier`.
```xml
-
<project xmlns="http://maven.apache.org/POM/4.0.0">
...
<dependencies>
@@ -92,6 +89,4 @@ To use the attached test JAR, specify a dependency on the main artifact with a s
</build>
...
</project>
-
```
-
diff --git a/content/markdown/guides/mini/guide-bash-m2-completion.md b/content/markdown/guides/mini/guide-bash-m2-completion.md
index e1c064c5..0a38869f 100644
--- a/content/markdown/guides/mini/guide-bash-m2-completion.md
+++ b/content/markdown/guides/mini/guide-bash-m2-completion.md
@@ -20,4 +20,3 @@ under the License.
# Guide to Maven auto completion using BASH
If you like having bash completion which i can recommend if you are working with Maven on command line i would suggest to install the following [Maven Bash Auto Completion](https://github.com/juven/maven-bash-completion) to fullfil you needs.
-
diff --git a/content/markdown/guides/mini/guide-building-for-different-environments.md b/content/markdown/guides/mini/guide-building-for-different-environments.md
index 10eb1ecf..de197bbc 100644
--- a/content/markdown/guides/mini/guide-building-for-different-environments.md
+++ b/content/markdown/guides/mini/guide-building-for-different-environments.md
@@ -36,7 +36,6 @@ Note:
resources/
test/
java/
-
```
Under `src/main/resources` there are three files:
@@ -98,7 +97,6 @@ Under `src/main/resources` there are three files:
.. Other profiles go here ..
</profiles>
-
```
Three things are configured in this snippet:
@@ -120,4 +118,3 @@ Under `src/main/resources` there are three files:
1. [Introduction to Build Profiles](../introduction/introduction-to-profiles.html)
2. [Standard Directory Layout](../introduction/introduction-to-the-standard-directory-layout.html)
-
diff --git a/content/markdown/guides/mini/guide-configuring-maven.md b/content/markdown/guides/mini/guide-configuring-maven.md
index 56c55488..051f32e9 100644
--- a/content/markdown/guides/mini/guide-configuring-maven.md
+++ b/content/markdown/guides/mini/guide-configuring-maven.md
@@ -126,4 +126,3 @@ You can encrypt passwords in your settings file. However, you must first configu
### Toolchains
You can build a project using a specific version of JDK independent from the one Maven is running with. For more information, see the [Guide to Using Toolchains](./guide-using-toolchains.html).
-
diff --git a/content/markdown/guides/mini/guide-configuring-plugins.md b/content/markdown/guides/mini/guide-configuring-plugins.md
index 5f78150a..ae8ede59 100644
--- a/content/markdown/guides/mini/guide-configuring-plugins.md
+++ b/content/markdown/guides/mini/guide-configuring-plugins.md
@@ -469,7 +469,7 @@ It's possible to bind multiple executions to the same phase, for example if you
Now, let us have another mojo example which shows a default lifecycle phase binding.
-```xml
+```java
@Mojo( name = "query", defaultPhase = LifecyclePhase.PACKAGE )
public class MyBoundQueryMojo
extends AbstractMojo
@@ -643,7 +643,6 @@ You can configure a reporting plugin using the `<reportSets>` tag. This is most
<reports/>
</reportSet>
</reportSets>
-
```
2. Refer to each Plugin Documentation (i.e. plugin-info.html) to know the available report goals.
@@ -667,4 +666,3 @@ Similar to the build plugins, to break the inheritance, you can use the `<inheri
...
</project>
```
-
diff --git a/content/markdown/guides/mini/guide-creating-archetypes.md b/content/markdown/guides/mini/guide-creating-archetypes.md
index da64c933..5bd7adf9 100644
--- a/content/markdown/guides/mini/guide-creating-archetypes.md
+++ b/content/markdown/guides/mini/guide-creating-archetypes.md
@@ -33,7 +33,6 @@ To create an archetype follow these steps:
An example `pom.xml` for an archetype artifact looks as follows:
```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>
@@ -53,7 +52,6 @@ An example `pom.xml` for an archetype artifact looks as follows:
</extensions>
</build>
</project>
-
```
All you need to specify is a `groupId`, `artifactId` and `version`. These three parameters will be needed later for invoking the archetype via `archetype:generate` from the commandline.
@@ -63,7 +61,6 @@ All you need to specify is a `groupId`, `artifactId` and `version`. These three
The [archetype descriptor](/archetype/archetype-models/archetype-descriptor/archetype-descriptor.html) is a file called `archetype-metadata.xml` which must be located in the `src/main/resources/META-INF/maven/` directory. An example of an archetype descriptor can be found in the quickstart archetype:
```xml
-
<archetype-descriptor
xmlns="https://maven.apache.org/plugins/maven-archetype-plugin/archetype-descriptor/1.2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="https://maven.apache.org/plugins/maven-archetype-plugin/archetype-descriptor/1.2.0 https://maven.apache.org/xsd/archetype-descriptor-1.2.0.xsd"
@@ -77,7 +74,6 @@ The [archetype descriptor](/archetype/archetype-models/archetype-descriptor/arch
</fileSet>
</fileSets>
</archetype-descriptor>
-
```
The attribute `name` tag should be the same as the `artifactId` in the archetype `pom.xml`.
@@ -95,7 +91,6 @@ At this point one can only specify individual files to be created but not empty
Thus the quickstart archetype shown above defines the following directory structure:
```
-
archetype
|-- pom.xml
`-- src
@@ -113,7 +108,6 @@ archetype
`-- test
`-- java
`-- AppTest.java
-
```
## 3. Create the prototype files and the prototype pom.xml
@@ -123,7 +117,6 @@ The next component of the archetype to be created is the prototype `pom.xml`. An
An example for a prototype `pom.xml` is:
```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>
@@ -145,7 +138,6 @@ An example for a prototype `pom.xml` is:
</dependency>
</dependencies>
</project>
-
```
## 4. Install the archetype and run the archetype plugin
@@ -153,22 +145,18 @@ An example for a prototype `pom.xml` is:
Now you are ready to install the archetype:
```
-
mvn install
-
```
Now that you have created an archetype, you can try it on your local system by using the following command. In this command, you need to specify the full information about the archetype you want to use (its `groupId`, its `artifactId`, its `version`) and the information about the new project you want to create (`artifactId` and `groupId`). Don't forget to include the version of your archetype (if you don't include the version, you archetype creation may fail with a message that version:R [...]
```
-
mvn archetype:generate \
-DarchetypeGroupId=<archetype-groupId> \
-DarchetypeArtifactId=<archetype-artifactId> \
-DarchetypeVersion=<archetype-version> \
-DgroupId=<my.groupid> \
-DartifactId=<my-artifactId>
-
```
Once you are happy with the state of your archetype, you can deploy (or submit it to [Maven Central](/guides/mini/guide-central-repository-upload.html)) it as any other artifact and the archetype will then be available to any user of Maven.
@@ -186,4 +174,3 @@ mvn archetype:generate
```
Afterwhich, you can now customize the contents of the `archetype-resources` directory, and `archetype-metadata.xml`, then, proceed to Step#4 (Install the archetype and run the archetype plugin).
-
diff --git a/content/markdown/guides/mini/guide-default-execution-ids.md b/content/markdown/guides/mini/guide-default-execution-ids.md
index 5df69679..b5bb32ce 100644
--- a/content/markdown/guides/mini/guide-default-execution-ids.md
+++ b/content/markdown/guides/mini/guide-default-execution-ids.md
@@ -155,4 +155,3 @@ The resulting compiler-plugin configuration might look something like the follow
This example is fairly simple and straightforward. First, the `default-compile` execution sets the `source` and `target` values to `1.3` to allow older Java versions to run the project. Then, the `default-testCompile` execution resets the `source` and `target` values to `1.5`, which enables the project to use tools like TestNG that use annotations.
Incidentally, it's perhaps useful to point out that the example above is a little bit contrived; the compiler plugin targets Java 1.3 by default, so the only configuration that's really required is the `default-testCompile` execution. The `default-compile` execution respecifies plugin defaults. The only time this might be useful is when a parent POM defines a plugin-level configuration for `source` and `target` that needs to be changed for the purposes of these different compiler executi [...]
-
diff --git a/content/markdown/guides/mini/guide-deployment-security-settings.md b/content/markdown/guides/mini/guide-deployment-security-settings.md
index 6b270735..8522df26 100644
--- a/content/markdown/guides/mini/guide-deployment-security-settings.md
+++ b/content/markdown/guides/mini/guide-deployment-security-settings.md
@@ -26,7 +26,6 @@ In addition, some repositories may require authorisation to download from, so th
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:
```xml
-
<settings>
.
.
@@ -44,10 +43,8 @@ Which settings are required will depend on the type of repository you are deploy
.
.
</settings>
-
```
To encrypt passwords in these sections, refer to [Encryption Settings](./guide-encryption.html).
**Note**: The settings descriptor documentation can be found on the [Maven Local Settings Model Website](../../maven-settings/settings.html).
-
diff --git a/content/markdown/guides/mini/guide-encryption.md b/content/markdown/guides/mini/guide-encryption.md
index c89d61dd..ccd67c40 100644
--- a/content/markdown/guides/mini/guide-encryption.md
+++ b/content/markdown/guides/mini/guide-encryption.md
@@ -203,4 +203,3 @@ In Maven before version 3.2.1 you have to give the password on the command line
Starting with Maven 3.2.1, the password is an optional argument. If you omit the password, you will be prompted for it which prevents all the issues mentioned above.
We strongly recommend using Maven 3.2.1 and above to prevent problems with escaping special characters and of course security issues related to bash history or environment issues in relationship with the password.
-
diff --git a/content/markdown/guides/mini/guide-generating-sources.md b/content/markdown/guides/mini/guide-generating-sources.md
index dbfd3d4b..71379ab2 100644
--- a/content/markdown/guides/mini/guide-generating-sources.md
+++ b/content/markdown/guides/mini/guide-generating-sources.md
@@ -22,7 +22,6 @@ under the License.
Let's run though a short example. To generate sources you must first have a plugin that participates in the `generate-sources` phase like the [ANTLR4 Maven Plugin](https://www.antlr.org/api/maven-plugin/latest/). You configure its execution in the POM:
```xml
-
<project xmlns="http://maven.apache.org/POM/4.0.0">
...
<build>
@@ -44,8 +43,6 @@ Let's run though a short example. To generate sources you must first have a plug
</build>
...
</project>
-
```
When you type `mvn compile`, Maven walks through the [lifecycle](../introduction/introduction-to-the-lifecycle.html) and eventually hits the `generate-sources` phase. It sees that a plugin is configured that wants to participate in that phase, and executes the ANTLR4 Maven Plugin with the given configuration. Later, during the compile phase, all the code generated from the grammar files is compiled without further configuration.
-
diff --git a/content/markdown/guides/mini/guide-http-settings.md b/content/markdown/guides/mini/guide-http-settings.md
index f07e157f..7f0d20a6 100644
--- a/content/markdown/guides/mini/guide-http-settings.md
+++ b/content/markdown/guides/mini/guide-http-settings.md
@@ -188,7 +188,6 @@ Many of the configuration parameters for HttpClient have simple string values; h
<value2>,
<value3>,
...
-
```
As you may have noticed, this syntax is similar to the format-and-data strategy used by functions like `sprintf()` in many languages. The syntax has been chosen with this similarity in mind, to make it a little more intuitive to use.
@@ -363,4 +362,3 @@ The default timeout is 30 minutes. If you want to change this value, you can add
2. [HttpClient preference architecture and configuration guide](https://hc.apache.org/httpclient-3.x/preference-api.html)
3. [Guide to Wagon Providers](./guide-wagon-providers.html)
4. [Wagon Http](/wagon/wagon-providers/wagon-http/)
-
diff --git a/content/markdown/guides/mini/guide-large-scale-centralized-deployments.md b/content/markdown/guides/mini/guide-large-scale-centralized-deployments.md
index 40890892..a0129491 100644
--- a/content/markdown/guides/mini/guide-large-scale-centralized-deployments.md
+++ b/content/markdown/guides/mini/guide-large-scale-centralized-deployments.md
@@ -185,4 +185,3 @@ Both locations should have the mirror settings mentioned in [Managing Downloads
Typically, only continuous integration servers should have the deployment repository settings mentioned in [Managing Uploads to the Repository Manager](#Managing_Uploads_to_the_Repository_Manager), because only continuous integration servers should be allowed to upload to the repository manager. Alternatively, if you want developers to be able to upload artifacts to the repository manager, then include the deployment repository properties in the `settings.xml` files used by developers.
How the `settings.xml` files are stored and updated is beyond the scope of this document. The general recommendation is to manage a few `settings.xml` files centrally, and then use automation to distribute them to continuous integration servers and developer machines.
-
diff --git a/content/markdown/guides/mini/guide-maven-ci-friendly.md b/content/markdown/guides/mini/guide-maven-ci-friendly.md
index 772ba6e3..cb19ca2a 100644
--- a/content/markdown/guides/mini/guide-maven-ci-friendly.md
+++ b/content/markdown/guides/mini/guide-maven-ci-friendly.md
@@ -27,7 +27,6 @@ and/or `${changelist}` as placeholders for the version in your pom file.
This can look like this:
```xml
-
<project>
<modelVersion>4.0.0</modelVersion>
<parent>
@@ -64,7 +63,6 @@ This will become cumbersome over the time. So the other solution for this is
to simply use a property inside the pom file which looks like this:
```xml
-
<project>
<modelVersion>4.0.0</modelVersion>
<parent>
@@ -98,7 +96,6 @@ A note about the used properties. You can only use those named
named properties like this:
```xml
-
<project>
<modelVersion>4.0.0</modelVersion>
<parent>
@@ -122,7 +119,6 @@ to have more flexibility you can use a combination of the
different properties like this:
```xml
-
<project>
<modelVersion>4.0.0</modelVersion>
<parent>
@@ -172,7 +168,6 @@ build. We have a parent pom and one or more children.
The parent pom will look like this:
```xml
-
<project>
<modelVersion>4.0.0</modelVersion>
<parent>
@@ -198,7 +193,6 @@ The parent pom will look like this:
The child will look like this:
```xml
-
<project>
<modelVersion>4.0.0</modelVersion>
<parent>
@@ -223,7 +217,6 @@ The usual way of defining dependencies and their versions has been to use `${pro
So the correct way to do such things can be seen in the following example:
```xml
-
<project>
<modelVersion>4.0.0</modelVersion>
<parent>
@@ -249,7 +242,6 @@ So the correct way to do such things can be seen in the following example:
The child will look like this:
```xml
-
<project>
<modelVersion>4.0.0</modelVersion>
<parent>
@@ -280,7 +272,6 @@ Otherwise, you will install/deploy artifacts in the repository which will not be
Such a setup will look like this:
```xml
-
<project>
<modelVersion>4.0.0</modelVersion>
<parent>
@@ -340,4 +331,3 @@ When you are using Maven 4 with model version 4.1.0, you don't need to specify t
In addition, you don't need the [Flatten Maven Plugin][flatten-maven-plugin] like you did with Maven 3.
[flatten-maven-plugin]: https://www.mojohaus.org/flatten-maven-plugin/
-
diff --git a/content/markdown/guides/mini/guide-maven-classloading.md b/content/markdown/guides/mini/guide-maven-classloading.md
index 647a4766..a3049936 100644
--- a/content/markdown/guides/mini/guide-maven-classloading.md
+++ b/content/markdown/guides/mini/guide-maven-classloading.md
@@ -102,4 +102,3 @@ When a build plugin is executed, the thread's context classloader is set to the
Plugins are free to create further classloaders. For example, a plugin might want to create a classloader that combines the plugin class path and the project class path.
It is important to understand that the plugin classloader cannot load classes from any of those custom classloaders. Some factory patterns require that. Here you must add the classes to the plugin classloader as shown before.
-
diff --git a/content/markdown/guides/mini/guide-migration-to-mvn4.md b/content/markdown/guides/mini/guide-migration-to-mvn4.md
index 01023d7a..381280d2 100644
--- a/content/markdown/guides/mini/guide-migration-to-mvn4.md
+++ b/content/markdown/guides/mini/guide-migration-to-mvn4.md
@@ -340,4 +340,3 @@ If you want to execute a plugin before/after all or each of your (sub-)projects,
[cifriendlyguide]: https://maven.apache.org/guides/mini/guide-maven-ci-friendly.html
[flattenmavenplugin]: https://www.mojohaus.org/flatten-maven-plugin/
[bompomguide]: https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#bill-of-materials-bom-poms
-
diff --git a/content/markdown/guides/mini/guide-multiple-modules.md b/content/markdown/guides/mini/guide-multiple-modules.md
index c2dfd535..a594852e 100644
--- a/content/markdown/guides/mini/guide-multiple-modules.md
+++ b/content/markdown/guides/mini/guide-multiple-modules.md
@@ -63,4 +63,3 @@ Refer to the Maven command line interface reference for more information on thes
## More information
- [Chapter 6. A Multi-module Project (Maven by Example)](http://books.sonatype.com/mvnex-book/reference/multimodule.html)
-
diff --git a/content/markdown/guides/mini/guide-multiple-repositories.md b/content/markdown/guides/mini/guide-multiple-repositories.md
index 42df2d41..6b39949c 100644
--- a/content/markdown/guides/mini/guide-multiple-repositories.md
+++ b/content/markdown/guides/mini/guide-multiple-repositories.md
@@ -22,7 +22,6 @@ under the License.
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:
```xml
-
<project xmlns="http://maven.apache.org/POM/4.0.0">
...
<repositories>
@@ -39,7 +38,6 @@ There are two different ways that you can specify the use of multiple repositori
</repositories>
...
</project>
-
```
**NOTE:** You will also get the standard set of repositories as defined in the [Super POM](../introduction/introduction-to-the-pom.html#Super_POM).
@@ -47,7 +45,6 @@ There are two different ways that you can specify the use of multiple repositori
The other way you can specify multiple repositories is by creating a profile in the `${user.home}/.m2/settings.xml` or `${maven.home}/conf/settings.xml` file like the following:
```xml
-
<settings>
...
<profiles>
@@ -70,7 +67,6 @@ The other way you can specify multiple repositories is by creating a profile in
</activeProfiles>
...
</settings>
-
```
If you specify repositories in profiles you must remember to activate that particular profile! As you can see above we do this by registering a profile to be active in the `activeProfiles` element.
@@ -78,9 +74,7 @@ If you specify repositories in profiles you must remember to activate that parti
You could also activate this profile on the command like by executing the following command:
```
-
mvn -Pmyprofile ...
-
```
In fact the `-P` option will take a CSV list of profiles to activate if you wish to activate multiple profiles simultaneously.
@@ -109,4 +103,3 @@ Effective settings and local build POM, with profile taken into account, can eas
## Repository IDs
Each repository must have a **unique ID**. Clashing repository IDs within either effective settings or effective POMs lead to build failures. However, repositories from POM get overwritten by repositories with the same ID from effective settings. Repository IDs are also used in the [local repository metadata](https://maven.apache.org/ref/3-LATEST/maven-repository-metadata/).
-
diff --git a/content/markdown/guides/mini/guide-multiple-subprojects-4.md b/content/markdown/guides/mini/guide-multiple-subprojects-4.md
index 52dc87cc..c6cc3222 100644
--- a/content/markdown/guides/mini/guide-multiple-subprojects-4.md
+++ b/content/markdown/guides/mini/guide-multiple-subprojects-4.md
@@ -179,4 +179,3 @@ as depicted above.
* [Chapter 6. A Multi-module Project (Maven by Example)](http://books.sonatype.com/mvnex-book/reference/multimodule.html) -
does not include Maven 4 changes!
-
diff --git a/content/markdown/guides/mini/guide-naming-conventions.md b/content/markdown/guides/mini/guide-naming-conventions.md
index 67330d90..0a325d1e 100644
--- a/content/markdown/guides/mini/guide-naming-conventions.md
+++ b/content/markdown/guides/mini/guide-naming-conventions.md
@@ -125,4 +125,3 @@ if one is defined in the [POM file][3].
[2]:https://semver.org/spec/v1.0.0.html
[3]:/pom.html#Repository
[4]:/pom.html#Maven_Coordinates
-
diff --git a/content/markdown/guides/mini/guide-new-committers.md b/content/markdown/guides/mini/guide-new-committers.md
index 4ea6291e..277d957b 100644
--- a/content/markdown/guides/mini/guide-new-committers.md
+++ b/content/markdown/guides/mini/guide-new-committers.md
@@ -26,4 +26,3 @@ While this process is sorting itself out it is recommended that you peruse the v
Of particular interest is the [Committer's FAQ](http://www.apache.org/dev/committers.html) and the [New Committer's Guide](http://www.apache.org/dev/new-committers-guide.html).
If you have any questions please feel free to ask any of the Maven developers.
-
diff --git a/content/markdown/guides/mini/guide-proxies.md b/content/markdown/guides/mini/guide-proxies.md
index afc5832f..9e9aaef9 100644
--- a/content/markdown/guides/mini/guide-proxies.md
+++ b/content/markdown/guides/mini/guide-proxies.md
@@ -24,7 +24,6 @@ You can configure a proxy to use for some or all of your HTTP requests with Mave
The `nonProxyHosts` setting accepts wild cards, and each host not to proxy is separated by the | character. This matches the JDK configuration equivalent.
```xml
-
<settings>
.
.
@@ -43,7 +42,6 @@ The `nonProxyHosts` setting accepts wild cards, and each host not to proxy is se
.
.
</settings>
-
```
Please note that currently NTLM proxies are not supported as they have not been tested. Some transports allow to use the relevant Java system properties to make this work, but that approach is specific for given implementation, and should not be considered the "official" way of configuring proxies.
@@ -52,4 +50,3 @@ Please note that currently NTLM proxies are not supported as they have not been
1. [Settings descriptor documentation](../../maven-settings/settings.html)
2. [Configuring Maven](./guide-configuring-maven.html)
-
diff --git a/content/markdown/guides/mini/guide-releasing.md b/content/markdown/guides/mini/guide-releasing.md
index e5f29307..4678c09b 100644
--- a/content/markdown/guides/mini/guide-releasing.md
+++ b/content/markdown/guides/mini/guide-releasing.md
@@ -240,4 +240,3 @@ This is because your `~user/.ssh/known_hosts` file doesn't have the host listed.
### The site deploy goal hangs
First, this means that you have successfully deployed the artifacts to the remote repo and that it's only the site deployment that is now an issue. Stop your build, cd to **target/checkout**> and run the build again by executing `mvn site:deploy`. You should see a prompt asking you to enter a password. This happens if your key is not in the authorized keys on the server.
-
diff --git a/content/markdown/guides/mini/guide-relocation.md b/content/markdown/guides/mini/guide-relocation.md
index 4561daff..909c509e 100644
--- a/content/markdown/guides/mini/guide-relocation.md
+++ b/content/markdown/guides/mini/guide-relocation.md
@@ -52,7 +52,6 @@ The goal of the example below is for the `foo` project to relocate its groupId f
</relocation>
</distributionManagement>
</project>
-
```
In this case we are relocating because the groupId has changed. We only need to add the element that has changed to the `relocation` element. For information on which elements are allowed in the `relocation` element, see [the POM reference](/ref/current/maven-model/maven.html#class_relocation).
@@ -152,4 +151,3 @@ $ mvn dependency:list dependency:tree
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
```
-
diff --git a/content/markdown/guides/mini/guide-repository-ssl.md b/content/markdown/guides/mini/guide-repository-ssl.md
index 9a70d27f..ef94eb93 100644
--- a/content/markdown/guides/mini/guide-repository-ssl.md
+++ b/content/markdown/guides/mini/guide-repository-ssl.md
@@ -116,4 +116,3 @@ MAVEN_OPTS="-Xmx512m -Djavax.net.ssl.trustStore=trust.jks \
The following links may be useful in understanding SSL infrastructure management in Java:
- [HttpClient](http://hc.apache.org/httpclient-3.x/sslguide.html)'s SSL guide
-
diff --git a/content/markdown/guides/mini/guide-reproducible-builds.md b/content/markdown/guides/mini/guide-reproducible-builds.md
index b881a4f8..0980fbc0 100644
--- a/content/markdown/guides/mini/guide-reproducible-builds.md
+++ b/content/markdown/guides/mini/guide-reproducible-builds.md
@@ -106,4 +106,3 @@ Don't hesitate to share your questions or solutions on [user mailing-list](/mail
- Q. Which additional plugins need to be updated for Reproducible Builds?
A. See the list of [required upgrades](/plugins/maven-artifact-plugin/plugin-issues.html)
-
diff --git a/content/markdown/guides/mini/guide-site.md b/content/markdown/guides/mini/guide-site.md
index 6e4ed77f..9df520d9 100644
--- a/content/markdown/guides/mini/guide-site.md
+++ b/content/markdown/guides/mini/guide-site.md
@@ -282,4 +282,3 @@ To add your own content for that translation instead of using the default, place
```
With one site descriptor per language, the translated site(s) can evolve independently.
-
diff --git a/content/markdown/guides/mini/guide-snippet-macro.md b/content/markdown/guides/mini/guide-snippet-macro.md
index 047c27b6..65cd50bd 100644
--- a/content/markdown/guides/mini/guide-snippet-macro.md
+++ b/content/markdown/guides/mini/guide-snippet-macro.md
@@ -89,4 +89,3 @@ As of doxia-core version 1.0-alpha-9, a 'file' parameter is also available. If a
- Macros in apt **must not** be indented.
- Exactly one of `url` or `file` **must** be specified.
-
diff --git a/content/markdown/guides/mini/guide-using-ant.md b/content/markdown/guides/mini/guide-using-ant.md
index e43f8e3f..be60626b 100644
--- a/content/markdown/guides/mini/guide-using-ant.md
+++ b/content/markdown/guides/mini/guide-using-ant.md
@@ -22,7 +22,6 @@ under the License.
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 _execution/_ section and specifying a new phase.
```xml
-
<project xmlns="http://maven.apache.org/POM/4.0.0">
<modelVersion>4.0.0</modelVersion>
<artifactId>my-test-app</artifactId>
@@ -56,13 +55,11 @@ The example above illustrates how to bind an ant script to a lifecycle phase. Yo
</plugins>
</build>
</project>
-
```
So a concrete example would be something like the following:
```xml
-
<project xmlns="http://maven.apache.org/POM/4.0.0">
<modelVersion>4.0.0</modelVersion>
<artifactId>my-test-app</artifactId>
@@ -95,6 +92,4 @@ So a concrete example would be something like the following:
</plugins>
</build>
</project>
-
```
-
diff --git a/content/markdown/guides/mini/guide-using-extensions.md b/content/markdown/guides/mini/guide-using-extensions.md
index aeb849cd..3f07a944 100644
--- a/content/markdown/guides/mini/guide-using-extensions.md
+++ b/content/markdown/guides/mini/guide-using-extensions.md
@@ -42,7 +42,6 @@ There are different means of loading extensions depending on the type. There are
Example:
```xml
-
<project xmlns="http://maven.apache.org/POM/4.0.0">
...
<build>
@@ -59,15 +58,12 @@ There are different means of loading extensions depending on the type. There are
</build>
...
</project>
-
-
```
- Registered as build extension in [`project->build->extensions->extension`](../../pom.html#Extensions)
Example:
```xml
-
<project xmlns="http://maven.apache.org/POM/4.0.0">
...
<build>
@@ -81,7 +77,5 @@ There are different means of loading extensions depending on the type. There are
</build>
...
</project>
-
-
```
diff --git a/content/markdown/guides/mini/guide-using-modello.md b/content/markdown/guides/mini/guide-using-modello.md
index 8b6b46db..122116eb 100644
--- a/content/markdown/guides/mini/guide-using-modello.md
+++ b/content/markdown/guides/mini/guide-using-modello.md
@@ -34,7 +34,6 @@ A typical modello model looks like the following:
To utilize Modello, you would configure the `modello-maven-plugin` something like the following where you want to generate the Java sources for the model, the xpp3 serialization code and the xpp3 deserialization code (see [modello-plugin-xpp3](https://codehaus-plexus.github.io/modello/modello-plugins/modello-plugin-xpp3/) for more details):
```xml
-
<project xmlns="http://maven.apache.org/POM/4.0.0">
...
<build>
@@ -67,6 +66,4 @@ To utilize Modello, you would configure the `modello-maven-plugin` something lik
</build>
...
</project>
-
```
-
diff --git a/content/markdown/guides/mini/guide-using-one-source-directory.md b/content/markdown/guides/mini/guide-using-one-source-directory.md
index 0d6c5221..c2d64ace 100644
--- a/content/markdown/guides/mini/guide-using-one-source-directory.md
+++ b/content/markdown/guides/mini/guide-using-one-source-directory.md
@@ -159,4 +159,3 @@ Source directories aside, sometimes people desire to produce multiple JARs from
- If you are looking to produce JARs that are different (i.e., they have their own dependencies and metadata), Maven doesn't support this. This usually is only needed when sharing a source directory for intrinsically different things, so the use case above applies instead.
- If you are producing a JAR that is a derivative of the original (e.g., just a subset of classes, or the same JAR with debugging enabled), Maven supports this using profiles. See [Introduction to Profiles](../introduction/introduction-to-profiles.html) for more information.
-
diff --git a/content/markdown/guides/mini/guide-using-toolchains.md b/content/markdown/guides/mini/guide-using-toolchains.md
index 80d2eac0..15021138 100644
--- a/content/markdown/guides/mini/guide-using-toolchains.md
+++ b/content/markdown/guides/mini/guide-using-toolchains.md
@@ -134,4 +134,3 @@ Starting with [Maven 3.3.1](/docs/3.3.1/release-notes.html) you can put the `too
```
You can configure as many toolchains as you want in your `toolchains.xml` file.
-
diff --git a/content/markdown/guides/mini/guide-wagon-providers.md b/content/markdown/guides/mini/guide-wagon-providers.md
index 89268ea3..67b3b2d8 100644
--- a/content/markdown/guides/mini/guide-wagon-providers.md
+++ b/content/markdown/guides/mini/guide-wagon-providers.md
@@ -68,4 +68,3 @@ Maven 2.2.1 provides two providers for HTTP/HTTPS Wagons: `lightweight` and `htt
```
**NOTE:** The default provider for HTTP/HTTPS Wagons is `lightweight`.
-