[
https://issues.apache.org/jira/browse/MNG-8337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892316#comment-17892316
]
Guillaume Nodet commented on MNG-8337:
--------------------------------------
Fwiw, the problem does not happen when running the following command using
4.0.0-beta-5:
{code}
mvn clean artifact:describe-build-output -b concurrent -T 1
{code}
> aggregator goal called from CLI shows an additional module at end (= first
> module twice)
> ----------------------------------------------------------------------------------------
>
> Key: MNG-8337
> URL: https://issues.apache.org/jira/browse/MNG-8337
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.6.3, 3.9.9, 4.0.0-beta-5
> Reporter: Herve Boutemy
> Priority: Major
>
> example with this surprising {{{}[13/12]{}}}:
> {noformat}
> [INFO] ------------------< eu.maveniverse.maven.nisse:nisse
> >------------------
> [INFO] Building eu.maveniverse.maven.nisse:nisse 0.3.3
> [1/12]
> [INFO] from pom.xml
> [INFO] --------------------------------[ pom
> ]---------------------------------
> [INFO]
> [INFO] --- clean:3.4.0:clean (default-clean) @ nisse ---
> ...
> [INFO] ------------------< eu.maveniverse.maven.nisse:nisse
> >------------------
> [INFO] Building eu.maveniverse.maven.nisse:nisse 0.3.3
> [13/12]
> [INFO] from pom.xml
> [INFO] --------------------------------[ pom
> ]---------------------------------
> [INFO]
> [INFO] --- artifact:3.5.2:describe-build-output (default-cli) @ nisse ---
> {noformat}
> in fact, it is not a 13th module but the first module where an aggregator
> goal has to run ({{{}artifact:describe-build-output{}}}), without any other
> lifecycle goal as they already have been executed on {{[1/12]}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
