gnodet opened a new pull request, #14002:
URL: https://github.com/apache/maven/pull/14002

   Backport of #13559 to `maven-4.0.x`.
   
   When the concurrent builder detects that a project uses a plugin that is
   also a reactor module, it now un-skips the plugin project's READY phase
   and all its transitive predecessor steps (including cross-project
   dependencies such as reactor libraries the plugin compiles against).
   
   Previously, requesting a phase before `compile` (e.g. `initialize`) left
   the plugin project's READY step skipped, so the plugin JAR was never built
   and resolution failed.
   
   ## Changes
   
   - **`BuildPlanExecutor`**: after wiring `PLAN(consumer) → READY(plugin)`, 
call
     `readyStep.allPredecessors().filter(s -> s.skip.get()).forEach(s -> 
s.skip.set(false))`
     to clear all skipped steps transitively — including cross-project library 
dependencies.
   - **`BuildPlanCreatorTest`**: two new unit tests for the two-project case 
(plugin + consumer)
     and the three-project case (library + plugin + consumer).
   - **`MavenITmng1088ReactorPluginResolutionTest`**: re-enabled (was 
`@Disabled` for MNG-7977);
     updated to use `-b concurrent initialize` to test the exact scenario.
   - **mng-1088 IT fixture**: migrated to Maven 4 API (`maven-api-core` + 
`maven-api-di`,
     implements `Mojo`) and POM 4.1.0 format with `subprojects`/`root` so the 
plugin loads
     correctly from `target/classes/`.
   
   Equivalent of merge commit a85dd49cb377aca7cbcca0dae071fe07b816e3b6.
   
   <!-- maven-backport-bot -->


-- 
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]

Reply via email to