[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17535889#comment-17535889 ]
ASF GitHub Bot commented on MNG-7433: ------------------------------------- gnodet commented on PR #730: URL: https://github.com/apache/maven/pull/730#issuecomment-1124575847 > Please create a separate ticket for this. For what exactly ? The terminal width thing ? You'd prefer the terminal width adjustment to be only in 3.9.x / master ? > Question: I guess this must also go into 3.9.0 and master? Yes, the warning should be in all 3 supported branches. Fwiw, I've committed the improvement with the terminal width. The thread safety warning now looks like the following in my terminal: ``` [INFO] -----------------------< org.apache.maven:maven >----------------------- [INFO] Building Apache Maven 3.8.6-SNAPSHOT [1/15] [INFO] --------------------------------[ pom ]--------------------------------- [WARNING] ******************************************************************************************************************************************************************* [WARNING] * Your build is requesting parallel execution, but project contains the following plugin(s) that have goals not marked as @threadSafe to support parallel * [WARNING] * building. * [WARNING] * While this /may/ work fine, please look for plugin updates and/or request plugins be made thread-safe. * [WARNING] * If reporting an issue, report it against the plugin in question, not against maven-core. * [WARNING] ******************************************************************************************************************************************************************* [WARNING] The following plugins are not marked @threadSafe in Apache Maven: [WARNING] - org.apache.rat:apache-rat-plugin:0.13 [WARNING] Enable debug to see more precisely which goals are not marked @threadSafe. [WARNING] ******************************************************************************************************************************************************************* [INFO] ``` Btw, having maven displaying such warnings during its own build... !! > [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 > Assignee: Guillaume Nodet > 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)