It relies on gradlew and gradle maven plugin, i.e. your git dependencies should be ready so that the plugin can do gradlew install in the local maven repository after fetching from git for you…
This is really useful. Unfortunately our project is on hold atm due to other reasons. As soon as we will continue I will have a look at this more closely, but after reading readme on github I think this is interesting.
It might also be of good input for Gradle devs, as they mentioned earlier about supporting such a feature in Gradle core one day.
Yep, it’s part of our long-term plan to make it very easy to substitute pre-built binaries for locally built projects and vice versa. So a project dependency could be fulfilled by a downloaded artifact, or by an artifact built locally. A lot of the current work on “project decoupling” is heading toward this goal.