Aggregator and module POMs at root folder

[gwenn]

Hello, there is an issue with the following structure:

.
├── mod1
│   ├── pom.xml
│   └── src
│       └── main
│           └── java
│               └── ...
├── mod2
│   ├── pom.xml
│   └── src
│       └── main
│           └── java
│               └── ...
├── mod3.xml # application POM with pom.xml as parent and dependencies mod1, mod2
├── pom.xml # aggregator / parent POM with modules mod3.xml, mod1, mod2
├── src # mod3 sources
│   └── main
│       └── java
│           └── ...

If aggregator / parent POM is touched, mvn releaser:release deploys only parent pom (and mod1, mod2 jars) but not mod3 jar.

[INFO] --- multi-module-maven-release-plugin:3.6.4:release (default-cli) @ parent ---
[INFO] Will use version 1.1.5 for parent as it has changed since the last release.
[INFO] Releasing mod1 0.4.7 as parent has changed.
[INFO] Releasing mod2 0.3.7 as parent has changed.
[INFO] Releasing mod3 0.1.9 as parent has changed.
[INFO] Going to release parent 1.1.5
[INFO] Going to release mod1 0.4.7
[INFO] Going to release mod2 0.3.7
[INFO] Going to release mod3 0.1.9
[INFO] Successfully written report file - version-report.json
[INFO] About to tag the repository with parent-1.1.5
[INFO] About to tag the repository with mod1-0.4.7
[INFO] About to tag the repository with mod2-0.3.7
[INFO] About to tag the repository with mod3-0.1.9
[INFO] About to run mvn [clean, deploy] with profiles [staging-deploy]
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] parent                                                             [pom]
[INFO] mod1                                                               [jar]
[INFO] mod2                                                               [jar]
[INFO]
...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] parent 1.1.5 ....................................... SUCCESS [  0.367 s]
[INFO] mod1 0.4.7 ......................................... SUCCESS [  0.851 s]
[INFO] mod2 0.3.7 ......................................... SUCCESS [  0.137 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
...

But when relaunched, mvn releaser:release deploys mod3 jar.

[INFO] --- multi-module-maven-release-plugin:3.6.4:release (default-cli) @ parent ---
[INFO] Will use version 1.1.5 for parent as it has not been changed since that release.
[INFO] Will use version 0.4.7 for mod1 as it has not been changed since that release.
[INFO] Will use version 0.3.7 for mod2 as it has not been changed since that release.
[INFO] can't resolve artifact: Could not find artifact org:mod3:jar:0.1.9 in artifactory (...)
...
[INFO] Will use version 0.1.10 for mod3 as although no change was detected, the artifact cannot be resolved!
[INFO] Going to release mod3 0.1.10
[INFO] Successfully written report file - version-report.json
[INFO] About to tag the repository with mod3-0.1.10
[INFO] About to run mvn [clean, deploy] with profiles [staging-deploy]
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS

Is it possible to have the aggregator / parent POM and a module POM at the root folder ?
Thanks.