I've been investigating why this test consistently fails for me: MavenSnapshotResolveIntegrationTest."can update snapshot artifact during build even if it is locked earlier in build consistently fails for me."

I found out that this test results depend on the content of my local maven repo (~/.m2/repository).

I happened to have in my local maven repo an artifact with the same coordinates as the one used in the test case: org.gradle:testproject:1.0-SNAPSHOT. This was causing test failures because different http requestes were issued to the test http sever. Instead of GET requests, I had HEAD requests due to the 'cache reuse' feature kicking in & reusing an unrelated artifact from a maven repo.

It was not quite easy to track so we might come up with a nicer handling for this case. For now, I've changed the artifact coordinates used in the test into something more unusual so that there's less risk of clash with existing content of m2 repo. Down the road we might grow our fixture to remove the problem completely (e.g. run build without cache reuse, etc.)