Hiteshsai007 opened a new pull request, #13612:
URL: https://github.com/apache/maven/pull/13612
### Description
This PR addresses #13517 by adding a Maven 4 API for executing a filtered
subset of a calculated lifecycle plan. It allows IDE embedders to select
configured mojo executions without reproducing Maven internal execution loops.
Issue: #13517
**How it works:**
I added a new `LifecycleExecutor` v4 service and a
`Session.executeLifecycle(project, tasks, filter)` shortcut. Maven first
calculates and configures the complete execution plan, then passes immutable v4
`MojoExecution` snapshots to the supplied predicate. The retained internal
executions are submitted to `MojoExecutor` in a single batch so dependency
resolution, lifecycle phase tracking, and execution order remain managed by
Maven. The previous current project is restored after execution, including
failure paths.
**Why this is necessary:**
Previously, IDE embedders such as m2e had to reproduce Maven internal
`MojoExecutor` loops to execute selected lifecycle entries. This coupled
embedders to mutable internal types and made them responsible for details such
as dependency context creation and phase tracking. This API keeps the mutable
execution objects inside Maven while exposing complete immutable metadata for
filtering.
**Testing:**
* Added `DefaultLifecycleExecutorTest` to verify that Maven filters the
calculated plan, executes the retained mojos as one unit, and restores the
previous current project.
* Successfully ran `mvn -pl impl/maven-core -am -DskipITs -Drat.skip=true
-Dtest=DefaultLifecycleExecutorTest -Dsurefire.failIfNoSpecifiedTests=false
test`. The 30-module focused reactor build passed with 1 test executed and no
failures.
* Formatting and Checkstyle completed successfully as part of the reactor
build.
---
<!--
Please open pull requests against one of the following branches:
- master — default target for all changes (new features + bug fixes).
If the change should also go to maven-4.0.x, request a backport in the PR.
- maven-3.10.x — target for 3.x changes (new features + bug fixes).
If the change should also go to maven-3.9.x, request a backport in the PR.
maven-3.9.x should receive only serious bug fixes, as it is approaching
EOL.
Backports are typically handled by maintainers;
however, after agreement you may open a separate backport PR to the target
maintenance branch.
-->
Following this checklist to help us incorporate your
contribution quickly and easily:
- [x] Your pull request should address just one issue, without pulling in
other changes.
- [x] Write a pull request description that is detailed enough to understand
what the pull request does, how, and why.
- [x] Each commit in the pull request should have a meaningful subject line
and body.
Note that commits might be squashed by a maintainer on merge.
- [x] Write unit tests that match behavioral changes, where the tests fail
if the changes to the runtime are not applied.
This may not always be possible but is a best-practice.
- [ ] Run `mvn verify` to make sure basic checks pass.
A more thorough check will be performed on your pull request automatically.
- [ ] You have run the [Core IT][core-its] successfully.
If your pull request is about ~20 lines of code you do not need to sign an
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the [Apache License Version 2.0, January
2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [x] I hereby declare this contribution to be licenced under the [Apache
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
- [ ] In any other case, please file an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).
[core-its]: https://maven.apache.org/core-its/core-it-suite/
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
