Hiteshsai007 opened a new pull request, #13647:
URL: https://github.com/apache/maven/pull/13647
### Description
This PR introduces a Maven 4 lifecycle participation SPI that allows
extensions to react after reactor projects are read, before and after each
project's execution, and when the build session ends.
Issue: #13514
**How it works:**
I added a new `LifecycleParticipant` SPI with structured
`ProjectExecutionEvent` callbacks that expose the Maven 4 `Session`, the
project being executed, its immutable `MojoExecution` plan, and an optional
failure. Maven discovers these participants after projects are read and
dispatches the callbacks through both the standard and concurrent lifecycle
engines. The participant contract is explicitly thread-safe and supplies the
project in each callback so extensions do not need mutable current-project
session state during parallel builds.
I also added `ProjectManager.setDependencies(...)`, allowing
`afterProjectsRead` implementations to update a project's direct dependencies
through the Maven 4 API before the reactor graph is rebuilt and sorted.
**Why this is necessary:**
Maven 4 extensions currently have to rely on legacy APIs such as
`AbstractMavenLifecycleParticipant` and `ProjectExecutionListener` for
lifecycle integration. Those APIs expose Maven 3 implementation types and do
not provide a Maven 4 SPI suitable for extensions such as Tycho and m2e. This
change provides the required lifecycle hooks, execution-plan visibility,
mutable reactor dependencies through `ProjectManager`, and a parallel-safe
per-project callback model.
**Testing:**
* Added tests verifying that a Maven 4 lifecycle participant can mutate
reactor dependencies and affect reactor ordering.
* Added tests covering `afterProjectsRead`, before/after project execution
callbacks, execution-plan visibility, successful completion state, and
session-end notification.
* Successfully passed `MavenLifecycleParticipantTest` (5 tests) and
`BuildPlanExecutorTest` (4 tests).
* Formatting and Checkstyle checks passed during the focused Maven 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 don't 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]
