-
mvn -U clean install
You can always try mvn -U clean install
-U forces a check for updated releases and snapshots on remote repositories.
run mvn install from the parent directory
This problem can occur if you have some child projects that refer to a parent pom and you have not installed from the parent pom directory (run mvn install from the parent directory). One of the child projects may depend on a sibling project and when it goes to read the pom of the sibling, it will fail with the error mentioned in the question unless you have installed from the parent pom directory at least once.
I just ran into this problem when moving a project to a new computer. I was in the habit of running commands from the child project and didn’t run install on the parent.