Hey Hans, You're right, there's no double compilation, I must have been so surprised everything suddenly worked with the latest build that I didn't notice the spring-beans project was being built.
Regarding the [ant.jar] warning, this is a strange warning given that I've now discovered that the jar is correctly being created. I'm not sure why the warning is being printed but in any case it's not correct. from zipTree(jar) works correctly. Thanks for your help Steven ________________________________ De : Hans Dockter <[email protected]> À : [email protected] Envoyé le : Lun 26 Octobre 2009, 22 h 12 min 43 s Objet : Re: [gradle-user] Next problem with Spring build On Oct 26, 2009, at 6:26 PM, Hans Dockter wrote: Thanks a lot Steven for all your feedback. > > >On Oct 26, 2009, at 5:50 PM, Steven Devijver wrote: > >Hey all, >> >> >>I've encountered the next problem with the Spring build. I'm using the latest >>build. For some reason which I can't identify Gradle compiles the depended >>upon projects twice (build fails on the second iteration). > > >Were is something compiled twice in the output below? > > >The modules/spring-beans/java15 project has no build.gradle for defining any >dependencies. Shouldn't there be one? If you type gradle -n you get a hierarchical dependency report. I have just improved the output for project dependencies in trunk (path instead of group/name/version). That should help to figure out this kind of problems. - Hans -- Hans Dockter Gradle Project Manager http://www.gradle.org
