You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Xavier Hanin (JIRA)" <ji...@apache.org> on 2007/12/06 15:36:43 UTC

[jira] Commented: (IVY-474) Conflict manager seems to not support dynamic revisions

    [ https://issues.apache.org/jira/browse/IVY-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549056 ] 

Xavier Hanin commented on IVY-474:
----------------------------------

FYI Ivy now provides a latest compatible conflict manager which is a kind of strict conflict manager but using a best effort strategy to find compatible modules (see IVY-648). This conflict manager deals with version ranges and latest versions.

> Conflict manager seems to not support dynamic revisions
> -------------------------------------------------------
>
>                 Key: IVY-474
>                 URL: https://issues.apache.org/jira/browse/IVY-474
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: unspecified
>         Environment: Ivy 1.5.0-incubating-dev-20070308022022 - 20070308022022
>            Reporter: Robert Macaulay
>             Fix For: 2.0
>
>
> If I use defaultConflictManager="strict"
> I get this
> [ extern | commons-logging | 1.1 ] (needed by [[ extern | spring-framework | 2.0.2 ], [ ubs | laredo | working@whou0128628 ]])
> conflicts with [ extern | commons-logging | [1.0.4,) ] (needed by [[extern | hibernate | 3.2.1 ]])
> It looks like the strict ConflictManager does not support dynamic ranges. 1.1 != [1.0.4,)  One package is requesting 1.1, the other is asking for 1.0.4 or greater. 

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