[
https://issues.apache.org/jira/browse/MNG-7476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17537422#comment-17537422
]
ASF GitHub Bot commented on MNG-7476:
-------------------------------------
gnodet commented on PR #736:
URL: https://github.com/apache/maven/pull/736#issuecomment-1127443478
Fwiw, I've reviewed the original MNG-7433 issue and especially the
reproducer and found out the issue was just a bug in the original project
locking and not simply a missing warning. The lock was acquired too early, so
that forked lifecycles could not obtain the lock for the project at all.
> Display a warning when an aggregator mojo is locking other mojo executions
> --------------------------------------------------------------------------
>
> Key: MNG-7476
> URL: https://issues.apache.org/jira/browse/MNG-7476
> Project: Maven
> Issue Type: Improvement
> Affects Versions: 3.8.5
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Priority: Major
> Fix For: 3.8.6, 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
