gnodet commented on pull request #578: URL: https://github.com/apache/maven/pull/578#issuecomment-940077448
> @famod I will do asap. At first glance, I wonder if this is somewhat related to https://issues.apache.org/jira/browse/MNG-7156 and #476. The problem and locking strategy are different, but if the problem is the access to the `MavenProject`, I wonder if #476 would solve both problems... I've tried to reproduce the problem with the latest `mvnd` which includes a fix similar to #476 with no success. I think this is to be expected since my PR provides an exclusive lock on a given project so that the same project can not be built twice in parallel (from the reactor and from a forked lifecycle), while your projects makes sure any plugin running as an aggregator can only run alone. @famod I think my proposal would not cause any delay in the build and that it should also fix the problem since the same project would not be build concurrently, thus the resolved artifacts should not be an issue. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
