On 19/01/2011, at 9:54 PM, Frank Wilson wrote: > > I would also add that (to me at least) it would be elegant if developers > didn't have to checkout > BuildCommon if they didn't intend to modify it. Instead it might be > referenced though Ivy. However > this is not definate requirement.
There are a couple of things we plan to do which might solve this problem: * Allow project dependencies to be used at configuration time. This is really just taking what is currently the special-case behaviour for the buildSrc project, and making it available for all projects in the build. * Allow a project dependency to be substituted with an external dependency at configuration time. This way, you could ask Gradle to use a project dependency if the BuildCommon stuff is checked out, or an external dependency if not. -- Adam Murdoch Gradle Developer http://www.gradle.org CTO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz
