gnodet opened a new issue, #13467: URL: https://github.com/apache/maven/issues/13467
Part of #13460 — Migrate Maven internals from v3 to v4 API ## Context Some areas can be migrated independently as quick wins, with no ordering dependencies on the larger phases. ## Quick Win 1: Event Loggers (~6 files) The v4 `ExecutionEvent` API already exists. The event loggers can be migrated to use it: - `PlainExecutionEventLogger` - `RichExecutionEventLogger` - `MachineExecutionEventLogger` - `RichBuildEventListener` These currently use v3 `MavenProject` / `MavenSession` through the v3 `ExecutionEvent` interface. ## Quick Win 2: `DefaultProject` Inversion `DefaultProject` (v4) currently wraps `MavenProject` (v3). It could hold v4 `Model` and other v4 types natively, constructing the `MavenProject` wrapper on demand. This is foundational for the Project Builder migration (#13461) but can be prototyped independently. ## Quick Win 3: `PluginParameterExpressionEvaluator` Could resolve expressions against v4 `Session` / `Project` while still producing v3-compatible results for plugin injection. This reduces v3 coupling in one of the most-used internal classes. ## Dependencies None — these can be picked up immediately. ## Complexity Low to medium per item. Good entry points for contributors new to the v4 migration effort. _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]
