[jira] Resolved: (IVY-648) latest compatible conflict manager

["Xavier Hanin (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IVY-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xavier Hanin resolved IVY-648.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0-beta-1

I've checked in an implementation of this a couple of days ago, it seems to be working well.

> latest compatible conflict manager
> ----------------------------------
>
>                 Key: IVY-648
>                 URL: https://issues.apache.org/jira/browse/IVY-648
>             Project: Ivy
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Xavier Hanin
>            Assignee: Xavier Hanin
>             Fix For: 2.0.0-beta-1
>
>
> The conflict manager system in Ivy is not currently flexible enough to deal with some complex compatibility issues in a dependency graph. Here is an example:
> #A;1.0-> { #B;[1.0,1.5] #C;[2.0,2.5] }
> #B;1.4->#D;1.5
> #B;1.5->#D;2.0
> #C;2.5->#D;[1.0,1.6]
> In this case, the current conflict manager system doesn't allow to end up with a set of compatible dependencies (#B;1.4 #C;2.5 and #D;1.5), because it requires:
> - adding additional constraints when a dynamic version constraint is resolved to an actual version
> - restarting the resolution process with such additional constraints when a compatibility conflict occurs
> Adding these two features and a conflict manager leveraging those to handle this use case would be a nice improvement to Ivy conflict management flexibility.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.