calle2010 commented on issue #594: URL: https://github.com/apache/maven-mvnd/issues/594#issuecomment-1038799982
I encountered a similar issue last week. See https://github.com/calle2010/mvdn-revision-issue for a minimal example with just a parent and a child pom. Steps to reproduce: 1. `mvnd clean install` builds version 1 of parent and child 2. change property revision to 2 in parent POM 3. `mvnd clean install` builds version 2 of parent and version 1 child (wrong) Reactor summary in this case is also different from mvn: [INFO] Reactor Summary: [INFO] [INFO] child 1 ............................................ SUCCESS [ 0.676 s] [INFO] parent 2 ........................................... SUCCESS [ 0.170 s] 4. `mvn clean install` builds version 2 of parent and child (correct) 5. `mvnd --stop; mvnd clean install` builds version 2 of parent and child (correct, but misses the point) Since it works correctly after `mvnd --stop` it seems to me as if something is cached in the daemon. Version information: mvnd native client 0.7.1-windows-amd64 (97c587c11383a67b5bd0ff8388bd94c694b91c1e) Terminal: org.jline.terminal.impl.jansi.win.JansiWinSysTerminal Apache Maven 3.8.3 (ff8e977a158738155dc465c6a97ffaf31982d739) Maven home: C:\Apps\mvnd\mvn Java version: 11.0.14, vendor: Eclipse Adoptium, runtime: C:\Apps\jdk11 Default locale: en_US, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" -- 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]
