Just got the ugliest workaround running. Having a multiproject that includes some projects, and every project having only external dependencies, it simply introduces before /compileJava/ a dependency on the maven install task for projects (within the multiproject) related to external dependencies.
It's only a raw attempt to mimic a sort of /smarter dependency resolution/. This workaround is only for multi-project builds... and that's a pity, but if I check out only a single project, it continues to build downloading dependencies from the maven repo. Any remark/suggestion? 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-tp4497854p4779056.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
