incubator-ivy-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Williams (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IVY-383) LatestRevisionStrategy has split personality
Date Thu, 11 Jan 2007 01:06:27 GMT

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

John Williams commented on IVY-383:
-----------------------------------

My patch helped, but not enough...

I'm stuck trying to deal with the fact that Ivy tries to resolve conflicts before it has a
version number for everything. This only appears to be a problem when the same module is both
a direct dependency and an indirect dependency and the indirect dependency is discovered first.
 For instance, suppose module C has been published with revisions 1.0 and 1.1, and B has been
published with a dependency on C where rev=1.0.  Now suppose module A depends on B and C with
rev=[1,).  You would expect A to use C with rev=1.1, but if B is listed first in the dependencies,
[1,) will be evicted by 1.0; by the time [1,) is resolved to 1.1, it's too late!

> LatestRevisionStrategy has split personality
> --------------------------------------------
>
>                 Key: IVY-383
>                 URL: https://issues.apache.org/jira/browse/IVY-383
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.4.1
>         Environment: all
>            Reporter: John Williams
>            Priority: Critical
>         Attachments: IVY-383-LatestConflictManager.patch
>
>
> LatestRevisionStrategy seems to compare both revision numbers and revision number patterns,
but the implementation of patterns broken.  For instance, patterns like "1.0+" are treated
specially, but patterns like "[1.0,)" are treated like literal revision numbers!  I have a
case in which this causes conflict resolution to produce incorrect results.  I'll hopefully
be posting a patch soon to fix the particular resolution problem I've found, but I'm suspicious
that there are other cases in which patterns are erroneously passed to LatestRevisionStrategy.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message