Skip to content
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.

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

Maven 4 Compatibility Testing #1986

Closed
wants to merge 2 commits into from
Closed

Conversation

gnodet
Copy link
Contributor

@gnodet gnodet commented Dec 16, 2024

A starting point for testing Maven 4 compatibility with a set of projects.
This currently scans all ASF projects for the ones that have a pom.xml ...
We may want to add some additional inclusions / exclusions...

@gnodet gnodet marked this pull request as draft December 16, 2024 13:14
@slawekjaranowski
Copy link
Member

We can also enable Maven4 by default in our builds - https://github.com/apache/maven-gh-actions-shared?tab=readme-ov-file#testing-with-maven-4

@gnodet
Copy link
Contributor Author

gnodet commented Dec 16, 2024

We can also enable Maven4 by default in our builds - https://github.com/apache/maven-gh-actions-shared?tab=readme-ov-file#testing-with-maven-4

I'm currently mostly interested in finding issues in Maven 4 rather than fixing our own builds, so I don't want to focus on Maven projects only.
I've created https://github.com/gnodet/maven4-testing whith in-progress testing results at gnodet/maven4-testing#133

@gnodet gnodet closed this Dec 16, 2024
@cstamas
Copy link
Member

cstamas commented Dec 16, 2024

We may want to add tool based on your findings, like:

  • up enforcer (if under some version) to the version that works with mvn4 (not to "latest")
  • same for exec-m-p
  • and so on...

All input on this are welcome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants