Since I'm refactoring our modules and transforming each of them in a single gradle project, I started considering them as single projects and linking them only through compile dependencies. At a certain point I thought I'd have to switch to a multi-module build and search for a way to obtain optional project dependencies (in a scenario where a developer checked out some modules and wants to modify them) while the scenario where the developer didn't checkout only a certain module and wants to resolve its dependencies through the dependency manager was always covered by the maven repo. Now: it's clear that I've not read enough about project deps/multi-module builds, but from your words I guess adding mavenLocal() to repositories and invoking the install command should be enough to share a packaged artifact in a local repo. The missing bit would be a way to automate the call to install command on save from IDE. Maybe STS has enough hooks fo that. I'll take a closer look.
Cheers Davide Szczepan Faber wrote: > > > Not sure what specifically would you like to know :) Consider a large, > hierarchical project consisting of 50+ modules. It should be easy to > check out / work with / build only the selected subproject(s). This > may mean the 'project dependencies' are satisfied via some repo > instead of being a part of a multi-module build run. > > -- 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-tp4497854p4499287.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
