[jira] [Commented] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other

["Juan Pablo Santos Rodríguez (Jira)" <ji...@apache.org>]

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

Juan Pablo Santos Rodríguez commented on MNG-7433:
--------------------------------------------------

After migrating to 3.8.5, seems that we have stumbled upon this issue too. 

In our case, a custom, thread-safe, aggregated mojo, which is bounded to generate-resources phase, gets locked when performing an mvn spring-boot:run -T 1C , but not when doing an mvn install -T 1C. The mojo itself isn't specially complicated, so the blocking issue seemed a bit puzzling.. At least some log warning explaining the issue would be very welcomed. In the meantime, we'll proceed to rewrite our custom mojos to non-aggregator.

> [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.7#820007)