[MNG-8337] aggregator goal called from CLI shows an additional module at end (= first module twice)
- Dominant language
- Java
- Stars
- 5.3k
- Forks
- 3.1k
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 297
Description
**[Hervé Boutemy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hboutemy)** opened **[MNG-8337](https://issues.apache.org/jira/browse/MNG-8337?redirect=false)** and commented
example with this surprising `{}[13/12]{`}:
```
[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 ---
```
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]`
---
**Affects:** 3.6.3, 3.9.9, 4.0.0-beta-5
**Issue Links:**
- [MNG-7991](https://issues.apache.org/jira/browse/MNG-7991) refactor "aggregator" goal feature
Contributor guide
Assessment
This issue has not been assessed yet.