pn-santos opened a new issue, #1481:
URL: https://github.com/apache/maven-mvnd/issues/1481
### Affected version
1.0.3
### Bug description
In a **multi-module** project, after the first (per `mvnd` instance) build
is run, e.g.
```
mvnd package
```
the (multi-module) parent pom seems to be persistently cached by `mvnd`.
Changes to the parent pom are simply ignored until the `mvnd` is restarted.
```
mvnd package
```
or even
```
mvnd clean package
```
will re-use the parent pom that was initially loaded.
If any of the modules pom files are changed though that is recognised by
`mvnd`. But the project parent pom seems to never be "refreshed" even if its
`pom.xml` change.
In a non multi-module project no such issue occurs.
If I use `mvn` I have no such issue.
My `mvnd` command is aliased to this (not sure if relevant):
```
mvnd -ntp \
-s path/to/maven/settings.xml \
-Dmaven.repo.local=path/to/local/repo \
-Daether.dependencyCollector.impl=bf
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
