I tried to answer on the other forum. Hopefully more people can answer. It is an interesting idea. I have wanted to do something like this too.
On Wed, Oct 9, 2013 at 2:39 AM, owahlen <owah...@googlemail.com> wrote: > Hello Jas, > Based on your suggestion I have moved the thread here: > > http://forums.gradle.org/gradle/topics/howto_change_transitive_dependency_into_project_dependency?rfm=1 > > The point is that "sub-project" and its transitive dependency > "sub-sub-project" are both located in a Maven repo. > Now a developer has "project" (which has a dependency on "sub-project") and > "sub-sub-project" checked out on his local disc. > > When he builds "project" gradle shall not resolve "sub-sub-project" from > the > maven repo but instead resolve it to the "sub-sub-project" on the local > disk > (i.e. a project dependency). > > If you now run "gradle eclipse" you will have a multi-project structure > that > allows you to efficiently refactor in both "project" and "sub-sub-project". > > > > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/howto-change-transitive-dependency-into-project-dependency-tp5711930p5711937.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 > > >
