[ https://issues.apache.org/jira/browse/MNG-6720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17635939#comment-17635939 ]
Hudson commented on MNG-6720: ----------------------------- Build unstable in Jenkins: Maven » Maven TLP » maven » PR-869 #3 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-869/3/ > MultiThreadedBuilder: wait for parallel running projects when using > --fail-fast > ------------------------------------------------------------------------------- > > Key: MNG-6720 > URL: https://issues.apache.org/jira/browse/MNG-6720 > Project: Maven > Issue Type: Bug > Components: Core > Affects Versions: 3.5.4, 3.6.1 > Reporter: Stefan Oehme > Assignee: Michael Osipov > Priority: Major > Fix For: 3.6.2 > > Time Spent: 40m > Remaining Estimate: 0h > > When a project fails using --fail-fast mode, other projects that are > currently running in parallel are not finished before the "session finished" > event is sent. This leads to issues for extensions that rely on the > documented order of events, which says that "session finished" is only sent > "after all projects have been finished/skipped". > In our case, we close a service on "session finished", and that service is > needed to execute goals. The goals that were running in parallel at that time > then fail, saying that our service was closed, giving our users the > impression that there is a bug in our code. > The relevant line is > [here|https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/lifecycle/internal/builder/multithreaded/MultiThreadedBuilder.java#L179]. > Instead of using `poll`, which simply returns when the parallel projects > aren't finished yet, the code should shut down the executor and wait for it > to complete the outstanding parallel work. -- This message was sent by Atlassian Jira (v8.20.10#820010)