[MNG-8186] Introduce flag for warning when an aggregator mojo is locking other mojo executions

**[Piotr Zygielo](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pzygielo)** opened **[MNG-8186](https://issues.apache.org/jira/browse/MNG-8186?redirect=false)** and commented

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

> This should not affect the build. And there's currently no way to avoid it.

---

**Affects:** 3.9.8

**Issue Links:**
- [MNG-7476](https://issues.apache.org/jira/browse/MNG-7476) Display a warning when an aggregator mojo is locking other mojo executions
(_**"is caused by"**_)

**Backported to:** [3.9.x-candidate](https://github.com/apache/maven/milestone/112?closed=1)

1 votes, 4 watchers

Start by reading MNG-7476 and the linked discussion, then reproduce the behavior on Maven 3.9.8. Done means Maven provides a documented flag for controlling the warning about an aggregator mojo locking other executions without affecting the build.

Written by the indexing model from the issue text.