>Now I had some problems with IDE integration. When I refresh gradle dependencies from STS it complains for UNRESOLVED DEPENDENCIES.
I suspect it's because the building of the data model for STS also happens in 'afterEvaluate' hook (in the ToolingApi). Do you mind trying out the gradle eclipse plugin instead? I think it should generate correct metadata files so you can import the project into Eclipse. Let me know how did it work. Cheers! On Thu, Sep 8, 2011 at 2:47 PM, davide.cavestro < [email protected]> wrote: > 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 version > > > Now 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 > > > -- Szczepan Faber Principal engineer@gradleware Lead@mockito
