gnodet commented on issue #13472: URL: https://github.com/apache/maven/issues/13472#issuecomment-6168323755
Cross-referencing #13499 (updated with m2e analysis) — the v4 execution service API should cover two m2e-specific requirements: 1. **Partial/filtered lifecycle execution**: m2e computes the full lifecycle plan, filters it (via lifecycle mapping metadata), then executes surviving mojos one-by-one because there's no API for "run this filtered subset of the plan." It manually reimplements `MojoExecutor`'s inner loop, calling `setupMojoExecution()` and `ensureDependenciesAreResolved()` per mojo. A proper API like `session.executePartialPlan(project, filteredMojoExecutions)` would let Maven handle phase-boundary dependency resolution and ordering correctly. 2. **Multi-session management**: m2e manages concurrent Maven sessions on different threads (one per project refresh). The embedding API needs to support session creation and concurrent execution without casting to `DefaultMaven`. _Claude Code on behalf of Guillaume Nodet_ -- 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]
