With gradle-1.0-milestone-4 it works!!!
To avoid concurrent modification exceptions I just had to decouple iteration
from the set of dependencies that's going to be modified. I did it with
/config.dependencies.withType(ExternalDependency)*.asList()*.each { dep ->/.
So this is the ultimate versionNow I had some problems with IDE integration. When I refresh gradle dependencies from STS it complains for UNRESOLVED DEPENDENCIES. I suppose STS inferences the dependencies from the DSL, so it is not aware of our dependencies replacement machinery (moreover I put it into the rootProject build script to share it with all subprojects). The funny thing is that it always fails resolving /testRuntime/ config deps: I guess STS uses that configuration (that in turn extends /runtime/ and /compile/) to collect all project dependencies and pass them to the ide project descriptor through its api. Maybe I should warn Kris De Volder from STS... BTW I will give a try to the /projects outside the build/ approach as soon as possible. Cheers Davide -- View this message in context: http://gradle.1045684.n5.nabble.com/Is-it-possible-to-elect-a-local-gradle-project-to-satisfy-other-projects-deps-tp4497854p4782279.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
