The Executor suite provides means to execute Maven 3 and Maven 4 programmatically, usually as part of some "integration builds" suite for some plugin or extensions, or Maven itself.
The dependency-less artifact maven-executor provides API and two executor
implementations out of the box: "forked" and "embedded". There are more providers in
providers/ sub-projects. In total, below is list of supported executors:
forkedOOTB withmaven-executorembeddedOOTB withmaven-executordocker-exeuses Docker CLI and runs Apache Maven Docker Imagetestcontainersuses Docker via TestContainers and runs Apache Maven Docker Image
Maven Executor 1.x line will contain only the executor bits, needed to run Maven ITs. Maven Executor 2.x line will add extra features a top of executors.
Development should happen against main branch. In case of need, improvements may be
back-ported to executor-1.x branch, to release patch releases, but in general, the
2.x line is under development.
You have found a bug, or you have an idea for a cool new feature? Contributing code is a great way to give something back to the open source community. Before you dig right into the code, there are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.
- Make sure you have a GitHub account.
- If you're planning to implement a new feature, it makes sense to discuss your changes on the dev list first. This way you can make sure you're not wasting your time on something that isn't considered to be in Apache Maven's scope.
- Submit a ticket for your issue, assuming one does not already exist.
- Clearly describe the issue, including steps to reproduce when it is a bug.
- Make sure you fill in the earliest version that you know has the issue.
- Fork the repository on GitHub.
We accept Pull Requests via GitHub. The developer mailing list is the
main channel of communication for contributors.
There are some guidelines which will make applying PRs easier for us:
- Create a topic branch from where you want to base your work (this is usually the master branch). Push your changes to a topic branch in your fork of the repository.
- Make commits of logical units.
- Respect the original code style: by using the same codestyle,
patches should only highlight the actual difference, not being disturbed by any formatting issues:
- Only use spaces for indentation.
- Create minimal diffs - disable on save actions like reformat source code or organize imports. If you feel the source code should be reformatted, create a separate PR for this change.
- Check for unnecessary whitespace with
git diff --checkbefore committing.
- Make sure you have added the necessary tests (JUnit/IT) for your changes.
- Run all the tests with
mvn -Prun-its verifyto assure nothing else was accidentally broken. - Submit a pull request to the repository in the Apache organization.
If you plan to contribute on a regular basis, please consider filing a contributor license agreement.