Fix #372. Synchronize access to rootProject.configurations to get around #372

[staffanf]

…that rootProject.configurations.classpath is created in a non thread-safe way

[uklance]

Interesting as you are only synchronising the "getter" logic. You are doing the mutation outside of the synchronized block

This seems to prove my theory that there's a bug in Gradle when resolving the root project's buildscript in a parallel build

[staffanf]

Yes, I would say here

The question is if it's the usage that's wrong or if the access should be thread-safe in gradle in the first place. That was kinda why I posted on the gradle forums hoping for some dev to notice.

[nedtwigg]

Interesting! Perhaps this PR and the issue it resolves will be helpful to the gradle folks. Thanks for your persistence and skeptical approach to a very tricky problem @staffanf and @uklance. Regardless of it gets fixed, we should merge this and keep it merged because it's nice to work with as many gradle versions as possible.

[nedtwigg]

Published in x.21.0