maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <>
Subject [jira] [Commented] (MNG-6720) MultiThreadedBuilder does not wait for outstanding projects to complete
Date Wed, 24 Jul 2019 21:40:00 GMT


Michael Osipov commented on MNG-6720:

Isn't that the point that is shall *not* wait for others, but fail as fast as possible?

> MultiThreadedBuilder does not wait for outstanding projects to complete
> -----------------------------------------------------------------------
>                 Key: MNG-6720
>                 URL:
>             Project: Maven
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.5.4, 3.6.1
>            Reporter: Stefan Oehme
>            Priority: Major
>          Time Spent: 10m
>  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|].
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

This message was sent by Atlassian JIRA

View raw message