Resolution: Won't Fix
Affects Version/s: 2.2.1
Fix Version/s: None
Component/s: Artifacts and Repositories
Number of attachments :
Since I didn't get any response to my comment on
MNG-4433, I've opened a new issue. The following is from my original comment.
I have exactly the same issue with 2.2.1. After changing and deploying parent POM, I run build with -U (on a different machine). Excerpt from output:
Maven says that it is downloading spock-parent POM, but it doesn't end up in the local repo. Compare to the output after manually deleting the old POM from the local repo:
Here we get "8K downloaded", which we didn't get before. The local repo now contains the correct POM, and the build succeeds.
Here is what the local repo looked like before I manually deleted the old POM:
As you can see, the POM's last modified date is recent, but nevertheless the content is old. In fact it still matches the pom.sha1, which was last updated in December! How is this possible?
This is a very insidious bug, and you would help a lot of people by fixing it ASAP.