Stefan Oehme created MNG-8648:
---------------------------------
Summary: Concurrent executor fires wrong ProjectStarted event
Key: MNG-8648
URL: https://issues.apache.org/jira/browse/MNG-8648
Project: Maven
Issue Type: Bug
Components: Core
Affects Versions: 4.0.0-rc-3
Reporter: Stefan Oehme
When using the new `-b concurrent` builder, the ProjectStarted event is fired
without the current project being set on the Session. This breaks all kinds of
event listeners in our Maven extension.
The code that [attaches the project
|https://github.com/apache/maven/blob/d7cada9c0b49c5f7ac7aced52498e354877333b1/impl/maven-core/src/main/java/org/apache/maven/lifecycle/internal/concurrent/BuildPlanExecutor.java#L378]to
the current Thread/Session currently only happens for the actual Mojo
execution, but not for the [Setup
step|https://github.com/apache/maven/blob/d7cada9c0b49c5f7ac7aced52498e354877333b1/impl/maven-core/src/main/java/org/apache/maven/lifecycle/internal/concurrent/BuildPlanExecutor.java#L378]
where the ProjectStarted event is fired.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
