[
https://issues.apache.org/jira/browse/IVY-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xavier Hanin resolved IVY-857.
------------------------------
Resolution: Fixed
Fix Version/s: 2.0-RC1
I've implemented, unit tested and documented this new feature. I think it
should address all the items in your comment Ernest, but I haven't tested it
extensively in real life situation. So Ernest I would appreciate if you could
give it a try and tell me if it works for your use cases.
> Better support for local builds
> -------------------------------
>
> Key: IVY-857
> URL: https://issues.apache.org/jira/browse/IVY-857
> Project: Ivy
> Issue Type: New Feature
> Components: Core
> Reporter: Xavier Hanin
> Assignee: Xavier Hanin
> Fix For: 2.0-RC1
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
