Major Description
Currently Ivy suggests to use a local filesystem resolver in a chain with returnFirst="true" to support local builds. It works well as long as you have control over the dependency revision requested, and can hence ask for a latest.integration version. But in some cases it would be nice to also override a transitive dependency, where do not control the requested revision.
Eg:
#A -> #B;1.0 -> #C;1.0
A developer work on #A and #C, and want to use a local build for #C. But this requires a local publication of #B too, just too override the dependency on #C. It would be better to have a resolver able to force the returned module for the dependency on #C to a locally published module, whatever the requested revision is.