[MNG-7476] Display a warning when an aggregator mojo is locking other mojo executions

[jira-importer]

Guillaume Nodet opened MNG-7476 and commented

---

Affects: 3.8.5

Issue Links:

• MNG-8186 Introduce flag for warning when an aggregator mojo is locking other mojo executions
  ("causes")

• MNG-7433 [REGRESSION] Multiple maven instances working on same source tree can lock each other

• MNG-250 make aggregation feasible

• MNG-6398 Multithread Build Hangs Execution with sonar:sonar goal when Aggregator POM references a Child Module as its Parent

• MNG-7487 Fix deadlock during forked lifecycle executions
  ("requires")

Remote Links:

• GitHub Pull Request #736
  
• Master commit
  
• 3.9.x commit
  

Backported to: 4.0.0-alpha-2, 3.9.0, 3.8.6

[jira-importer]

Guillaume Nodet commented

7da0214

5c0d6b9

0a94ff7

[jira-importer]

Piotr Zygielo commented

Can you share advice how to avoid/prevent this warning? If I see this in my parallel multi-module complex build - shall I expect bad result?

[jira-importer]

Guillaume Nodet commented

This should not affect the build.  And there's currently no way to avoid it.  We could introduce a flag if needed.

Ideally, we'll somehow refactor aggregator mojos in the future.

[jira-importer]

Piotr Zygielo commented

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

Perhaps the log level could be reconsidered then to demote it to INFO? (Would it be possible to select the level with the flag? It could be then explicitly decided by the build(er) - kind of accepting the state and have no warning for that?)

[jira-importer]

Piotr Zygielo commented

We could introduce a flag if needed.

I'd appreciate that if the current warning is unavoidable and not actionable.

[jira-importer]

Guillaume Nodet commented

Piotr Zygielo this issue is closed. Please create a follow-up issue to introduce a flag.  Maybe you could raise a PR to add such a flag ?