[jira] [Commented] (MNG-7156) Parallel build can cause issues between clean and forked goals

["David Elliott (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-7156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17585642#comment-17585642 ] 

David Elliott commented on MNG-7156:
------------------------------------

The added locking that allegedly fixed this issue seems to be causing my existing plugin code to deadlock.

My plugin code running as an ordinary mojo in one project creates MojoExecution for goals in other projects that have finished building.  I'm sure they've finished building because all of the projects are direct dependencies of the project running my mojo.

I then execute those executions in a ThreadPoolExecutor as part of some other work.  Without this change it worked, with this change I'm getting reports that it's deadlocked and the aggregator lock is somehow involved.

I have not had the chance to reproduce myself, and I will update this ticket with additional information when I am able.

Having code work just fine with Maven 3.8.4 and earlier, but deadlock in Maven 3.8.5 and 3.8.6 is not ideal.

> Parallel build can cause issues between clean and forked goals
> --------------------------------------------------------------
>
>                 Key: MNG-7156
>                 URL: https://issues.apache.org/jira/browse/MNG-7156
>             Project: Maven
>          Issue Type: Bug
>            Reporter: Guillaume Nodet
>            Assignee: Guillaume Nodet
>            Priority: Major
>             Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0
>
>
> Running {{mvn -T12 clean verify -Papache-release}} From [https://github.com/apache/jackrabbit-filevault] leads to various exceptions caused by the invocation of the {{clean}} goal.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)