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

Dan Tran commented on MNG-7433:
-------------------------------

per my finding,  i updated my mdev:sonar  ( the one that spins another mvn, 
invoker style) to nonagregating mojo, and can see the build runs more steps 
further at the other module running in another thread until it steps one of its 
 aggregating mojo (such as buildnumber-m-p) and stuck.  And just follow the 
same pattern to push more steps.  This means I need to ensure no aggregating 
mojos ( my own internal company mojo, and the ones from outside company) 

> [REGRESSION] Multiple maven instances working on same source tree can lock 
> each other
> -------------------------------------------------------------------------------------
>
>                 Key: MNG-7433
>                 URL: https://issues.apache.org/jira/browse/MNG-7433
>             Project: Maven
>          Issue Type: Bug
>    Affects Versions: 3.8.5
>            Reporter: Dan Tran
>            Priority: Major
>
> I have a large multi modules java maven build where:
>   * phase 1 - basic build + unit tests + jacoco  - 40 min
>   * phase 2 - sonar:sonar 20 min
>   * phase 3 - final packaging and basic smoke-test - 20 min
> To take advantage of Maven multi-threaded build, during the reactor build, 
> one of our maven module spins another instance of Maven to run sonar:sonar 
> goal right after the basic build is done. 
> This means  our phase 2 and phase 3 run in parallel sharing the same source 
> tree, same local maven repo (where sonar:sonar should have all needed 
> dependencies at the share local maven repo to run its task)
> With maven-3.8.5, parallelization is no longer possible, phase 3 is blocked 
> until phase 2 is done. 
> I am able to trace it to  https://github.com/apache/maven/pull/628 where the 
> locking started the happen
> How does the lock mechanic work?  there must be a local file where both Maven 
> instances are watching each other.  Is there an option to disable this lock?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to