Return-Path: 
 <ivy-user-return-6606-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-ivy-user-archive@www.apache.org
Received: (qmail 54838 invoked from network); 25 Mar 2010 14:06:42 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 25 Mar 2010 14:06:42 -0000
Received: (qmail 79309 invoked by uid 500); 25 Mar 2010 08:40:02 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 78965 invoked by uid 500); 25 Mar 2010 08:39:59 -0000
Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ivy-user-help@ant.apache.org>
List-Unsubscribe: <mailto:ivy-user-unsubscribe@ant.apache.org>
List-Post: <mailto:ivy-user@ant.apache.org>
List-Id: <ivy-user.ant.apache.org>
Reply-To: ivy-user@ant.apache.org
Delivered-To: mailing list ivy-user@ant.apache.org
Received: (qmail 78957 invoked by uid 99); 25 Mar 2010 08:39:58 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Mar 2010 08:39:58 +0000
X-ASF-Spam-Status: No, hits=1.2 required=10.0
	tests=AWL,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of david.herviou@gmail.com
 designates 209.85.220.212 as permitted sender)
Received: from [209.85.220.212] (HELO mail-fx0-f212.google.com)
 (209.85.220.212)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Mar 2010 08:39:54 +0000
Received: by fxm4 with SMTP id 4so3738991fxm.20
        for <ivy-user@ant.apache.org>; Thu, 25 Mar 2010 01:39:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:message-id:subject:from:to:content-type;
        bh=erK+/LZmGTlJ+KFtRSu4AQtvr7FdDo7qszryow0n5go=;
        b=s2Ehg5L8DAq47wiqN7az29EsFeaO1MbkaWo8oakDg96ujCfP73PH/6yU2lyHj/UorI
         lym/NXjNfTeUhq+ZotbZOhLZvy0Yt87fJU6ZF/n8pHIbLUMMHGmAsNSVCwQAcV9F1yd6
         nUxrAcw6UfNvyIHqbFSP4YCqBAoa2+OJeB8F4=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=W1Eov7lxop1QYjkkOPP78NyfAFUr5gdeLvpkv7njcGq/NHdIo1ho2lQNu68v19CgLN
         kXCFTVRAmIuqYfhg1l+gtQAEF5LDR9m+osrYxABFzBf3DOQkWOPerD6mipjJzu9ANNIH
         kMVmwfHt4mHkRQvU1HAObfsb0vpQHeBJ2ay68=
MIME-Version: 1.0
Received: by 10.223.143.21 with SMTP id s21mr663392fau.51.1269506371941; Thu,
	25 Mar 2010 01:39:31 -0700 (PDT)
In-Reply-To: <164626.92991.qm@web30808.mail.mud.yahoo.com>
References: <3fb233e51003220328p4aed57f7v9f4b05f3db285429@mail.gmail.com>
	 <164626.92991.qm@web30808.mail.mud.yahoo.com>
Date: Thu, 25 Mar 2010 09:39:31 +0100
Message-ID: <3fb233e51003250139g2d858333k1ae0bcbdf930771c@mail.gmail.com>
Subject: Re: Transitive resolving issue ?
From: david herviou <david.herviou@gmail.com>
To: ivy-user@ant.apache.org
Content-Type: multipart/alternative; boundary=0023545bd89c56f5d604829bfc53

--0023545bd89c56f5d604829bfc53
Content-Type: text/plain; charset=ISO-8859-1

A work-around is available by resolving conflict explicitly with something
like :
 <conflict org="module.org" module="moduleA" rev="moduleA.rev"/>
May help


2010/3/24 Maarten Coene <maarten_coene@yahoo.com>

> Seems like a bug to me.
> Could you create a new JIRA issue?
> https://issues.apache.org/jira/browse/IVY
>
> thanks,
> Maarten
>
>
>
>
> ----- Original Message ----
> From: david herviou <david.herviou@gmail.com>
> To: ivy-user@ant.apache.org
> Sent: Mon, March 22, 2010 11:28:54 AM
> Subject: Transitive resolving issue ?
>
> hello all,
>
> I'm running ivy since several months in my compagny and try to generalize
> its usage in all new project.
> Ivy version used is 2.1.0.
>
> Today we have encountered a problem while running the following use case (I
> mean the ivy:resolve task does not behave as expected) :
>
> moduleA has one of its dependencies like this : <dependency org="log4j"
> name="log4j" rev="1.2.14" transitive="false"/>
> moduleB has one of its dependencies like this : <dependency org="log4j"
> name="log4j" rev="1.2.15" transitive="false"/>
>
> While moduleC use moduleA and moduleB I have something like this :
> <dependency org="moduleA.org" name="moduleA" rev="moduleA.rev"/>
> <dependency org="moduleB.org" name="moduleB" rev="moduleB.rev"/>
>
> This seems to be very banal BUT, when running the ivy:resolve task the
> log4j-1.2.15 evicts the log4j-1.2.14 which seems to be a good thing!
> but thereafter the resolve task does not consider the transitivity has
> false
> and try to resolve all the dependencies of log4j-1.2.15
>
> If I remove moduleA.org and use only moduleB.org then the resolve task
> behave correctly (I mean there is no resolution of transitives
> dependencies).
> The reverse case is also true.
>
> Any idea ?
>
> David H.
>
>
>
>
>

--0023545bd89c56f5d604829bfc53--