This is an automated email from the ASF dual-hosted git repository.
sjaranowski pushed a commit to branch maven-plugin-testing-3.x
in repository https://gitbox.apache.org/repos/asf/maven-plugin-testing.git
The following commit(s) were added to refs/heads/maven-plugin-testing-3.x by
this push:
new 6a82de9 Remove maven-compat from dependencies
6a82de9 is described below
commit 6a82de978a634f6f164eedb0a171ce0651a7c8ce
Author: Slawomir Jaranowski <[email protected]>
AuthorDate: Mon Jan 5 13:32:59 2026 +0100
Remove maven-compat from dependencies
Not needed with Maven 3.9.12
---
maven-plugin-testing-harness/pom.xml | 17 -----------------
maven-plugin-testing-harness/src/site/markdown/index.md | 7 +++----
2 files changed, 3 insertions(+), 21 deletions(-)
diff --git a/maven-plugin-testing-harness/pom.xml
b/maven-plugin-testing-harness/pom.xml
index 49420cd..31faec2 100644
--- a/maven-plugin-testing-harness/pom.xml
+++ b/maven-plugin-testing-harness/pom.xml
@@ -87,23 +87,6 @@ under the License.
<version>${wagonVersion}</version>
<scope>provided</scope>
</dependency>
- <!--
- Keep this one as isolated as possible.
- But has to be present, as Maven 3 object graph is incomplete without it
- -->
- <dependency>
- <groupId>org.apache.maven</groupId>
- <artifactId>maven-compat</artifactId>
- <version>${mavenVersion}</version>
- <scope>runtime</scope>
- <optional>true</optional>
- <exclusions>
- <exclusion>
- <groupId>*</groupId>
- <artifactId>*</artifactId>
- </exclusion>
- </exclusions>
- </dependency>
<dependency>
<groupId>org.codehaus.plexus</groupId>
diff --git a/maven-plugin-testing-harness/src/site/markdown/index.md
b/maven-plugin-testing-harness/src/site/markdown/index.md
index 20f314b..9de97c5 100644
--- a/maven-plugin-testing-harness/src/site/markdown/index.md
+++ b/maven-plugin-testing-harness/src/site/markdown/index.md
@@ -21,9 +21,9 @@ date: February 2008
## Maven Plugin Testing Harness
- The Maven Plugin Testing Harness provides mechanisms to manage tests on
Mojos, i.e. by pre-constructing the [Plexus](http://plexus.codehaus.org)
components, providing stub objects for Maven functionality such as projects,
and populating fields from an XML file that resembles the plugin configuration
in the POM.
+The Maven Plugin Testing Harness provides mechanisms to manage tests on Mojos,
i.e. by pre-constructing the [Plexus](http://plexus.codehaus.org) components,
providing stub objects for Maven functionality such as projects, and populating
fields from an XML file that resembles the plugin configuration in the POM.
- The best way to start is to read the cookbook [How to use Maven Plugin
Testing Harness](./getting-started/index.html).
+The best way to start is to read the cookbook [How to use Maven Plugin Testing
Harness](./getting-started/index.html).
### Migration to 3.4.0
@@ -42,13 +42,12 @@ Therefore, some project dependencies have been set as
optional to avoid conflict
Your project should depend on the following artifacts, if needed:
- `org.codehaus.plexus:plexus-archiver` - used by `ArtifactStubFactory`
-- `org.apache.maven:maven-compat` - used by `MojoRule`
+- `org.apache.maven:maven-compat` - used by `MojoRule` (not needed with Maven
3.9.12+)
- `org.junit.jupiter:junit-jupiter-api` - used for JUnit 5 tests
- `junit:junit` - used for JUnit 3/4 tests
### Examples
-
The following examples shows how to use the Testing Harness in more advanced
use cases:
