Skip to content

Remove maven-compat from dependencies #256

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
slawekjaranowski merged 1 commit into from
Jan 5, 2026
Merged

Remove maven-compat from dependencies #256

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 0 additions & 17 deletions maven-plugin-testing-harness/pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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>
Expand Down
7 changes: 3 additions & 4 deletions maven-plugin-testing-harness/src/site/markdown/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand All @@ -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:


Expand Down