Return-Path: 
 <notifications-return-13051-apmail-ant-notifications-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org
Received: (qmail 21317 invoked from network); 9 Jul 2010 21:59:15 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 9 Jul 2010 21:59:15 -0000
Received: (qmail 63368 invoked by uid 500); 9 Jul 2010 21:59:15 -0000
Delivered-To: apmail-ant-notifications-archive@ant.apache.org
Received: (qmail 63314 invoked by uid 500); 9 Jul 2010 21:59:14 -0000
Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:notifications-help@ant.apache.org>
List-Unsubscribe: <mailto:notifications-unsubscribe@ant.apache.org>
List-Post: <mailto:notifications@ant.apache.org>
List-Id: <notifications.ant.apache.org>
Reply-To: dev@ant.apache.org
Delivered-To: mailing list notifications@ant.apache.org
Received: (qmail 63307 invoked by uid 99); 9 Jul 2010 21:59:14 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Jul 2010 21:59:14 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Jul 2010 21:59:11 +0000
Received: from thor (localhost [127.0.0.1])
	by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o69Lwnwb009382
	for <notifications@ant.apache.org>; Fri, 9 Jul 2010 21:58:50 GMT
Message-ID: <8525896.295701278712729378.JavaMail.jira@thor>
Date: Fri, 9 Jul 2010 17:58:49 -0400 (EDT)
From: "Payam Hekmat (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Updated: (IVY-1204) Dependency resolution fails if a
 dependency is resolved and a blacklisted revision is later transitively
 loaded
In-Reply-To: <14017138.295611278712129484.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


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

Payam Hekmat updated IVY-1204:
------------------------------

    Attachment: ivy-1204.patch
                ivy-1204-test.patch

Tentative patch and test case for the issue. 

I'm not entirely sure if my assumptions around VisitData, VisitNode and ResolveData are correct, but the patch passes the Ivy tests and the attached case. I'd appreciate any insights here. 

> 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.1.0, 2.2.0-RC1
>            Reporter: Payam Hekmat
>         Attachments: ivy-1204-test.patch, ivy-1204.patch
>
>
> 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.