ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Payam Hekmat (JIRA)" <j...@apache.org>
Subject [jira] Created: (IVY-1204) Dependency resolution fails if a dependency is resolved and a blacklisted revision is later transitively loaded
Date Fri, 09 Jul 2010 21:48:49 GMT
Dependency resolution fails if a dependency is resolved and a blacklisted revision is later
transitively loaded
---------------------------------------------------------------------------------------------------------------

                 Key: IVY-1204
                 URL: https://issues.apache.org/jira/browse/IVY-1204
             Project: Ivy
          Issue Type: Bug
          Components: Core
    Affects Versions: 2.2.0-RC1, 2.1.0
            Reporter: Payam Hekmat


Given 3 modules in the following configuration ('->' indicates a
dependency):
Module A: v1.0
          v1.1
Module B: v2.0
            ->A v1.0
          v2.1
            ->A v1.0
Module C: v3.0
            ->A v1.0
            ->B v2.1 
          v3.1
            ->A v1.1
            ->B v2.1 (yes, C v3.1 is technically impossible to resolve)

With an ivy file declaring the dependencies: 
        <dependency org="foo" name="A" rev="1.+" />
        <dependency org="foo" name="B"  rev="2.+" />
        <dependency org="foo" name="C"  rev="3.+" />

Using the 'latest-compatible' conflict manager, I'd expect it to resolve to A v1.0, B v2.0,
C v3.0, but it only resolves to B v2.1, C v3.1. If I change the order of the dependency elements
around (e.g. A,C,B or B,C,A), it resolves correctly. In the original order, it restarts the
resolve process trying to handle incompatibilities between A v1.0 and A v1.1. 


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


Mime
View raw message