Negative local Maven repo lookup persists after installing the artifact

[ppalaga]

Have a multimodule project with parent, common and app modules. app depends on common. All versions are 1.2.3-SNAPSHOT.

1. Remove all 1.2.3-SNAPSHOT artifacts from the local repo or upgrade to a new snapshot that is not present in local maven repo yet: mvn versions:set -DnewVersion=1.2.4-SNAPSHOT (I see this happening after releases).
2. Kill the daemon mvnd --stop
3. Try to build app cd app; mvnd compile It should fail, because common is not present in local repo
4. Rebuild the whole hierarchy: cd ..; mvnd clean install - success
5. Try to build the app module again: cd app; mvnd compile
   EXPECTED: It should pass, because common is present in local repo
   ACTUAL: Failed to execute goal on project app: Could not resolve dependencies for project app:1.2.3-SNAPSHOT: The following artifacts could not be resolved: common:jar:1.2.3-SNAPSHOT

Observation: App build succeeds when the daemon is restarted: mvnd --stop; cd app; mvnd compile

[gnodet]

The InvalidatingProjectArtifactsCache caches the exception and is not invalidated for some reason.