Return-Path: 
 <ivy-user-return-8926-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org>
X-Original-To: apmail-ant-ivy-user-archive@www.apache.org
Delivered-To: apmail-ant-ivy-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 154B011243
	for <apmail-ant-ivy-user-archive@www.apache.org>;
 Mon, 22 Sep 2014 21:13:19 +0000 (UTC)
Received: (qmail 15362 invoked by uid 500); 22 Sep 2014 21:13:18 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 15327 invoked by uid 500); 22 Sep 2014 21:13:18 -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 15315 invoked by uid 99); 22 Sep 2014 21:13:18 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Sep 2014 21:13:18 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of ionut.scutaru@gmail.com
 designates 74.125.82.171 as permitted sender)
Received: from [74.125.82.171] (HELO mail-we0-f171.google.com) (74.125.82.171)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Sep 2014 21:12:52 +0000
Received: by mail-we0-f171.google.com with SMTP id k48so3573658wev.30
        for <ivy-user@ant.apache.org>; Mon, 22 Sep 2014 14:12:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        bh=nr7PPJ/aX/GQCzdjvWH/W+BKF+o2E0ba3OrtloOtMCA=;
        b=pl6f6K5L5EDhPpLLytd0TDZYUZ0ipTZoFUH/ByCAPTa4PHiBn09S8GPdxmmMN0NsMl
         aCP9b4bYMWVIW3YcE6yqbVJkK71YfbsAcL/tcdgfs+JZefE1/GkhVP36ESwxvYtMyYs8
         nbU8yw7eLmKG+oHuSJIlohdjDEIFunlflOzeSOkcnonXWgAZQmuMv6XHC1i/QNDx7K38
         +WdHaBlm08oFTGgfaAxNZ+8r1SzH0OMn/VeIrsya8WFWQvnDD95uVfGnfoJ+43iuHG/a
         aCih/4GgrzLcqk6BYnXF6qo4x098vxbqqPtnBDu6FpF2ZtOcDUu0oVagWnBIf0sK2ew3
         MNYg==
X-Received: by 10.180.211.137 with SMTP id nc9mr7965037wic.47.1411420371375;
 Mon, 22 Sep 2014 14:12:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.110.34 with HTTP; Mon, 22 Sep 2014 14:12:31 -0700 (PDT)
In-Reply-To: 
 <CADRQvsa8sPiyjFhfw7C-aLxA6-iLS2d-JUHVyGMBM6uzXonAMQ@mail.gmail.com>
References: 
 <CAFCfRH7SoTwJEjhzDh93shRKojAi-GoxS8M_QNpmQ=VvzFSYkQ@mail.gmail.com>
 <CADRQvsZ3b=5LCM9XQ5gibf5Lu2OSU8dH_fQxkbFsM9uJYYT9Uw@mail.gmail.com>
 <CADRQvsa8sPiyjFhfw7C-aLxA6-iLS2d-JUHVyGMBM6uzXonAMQ@mail.gmail.com>
From: Ionut Scutaru <ionut.scutaru@gmail.com>
Date: Tue, 23 Sep 2014 00:12:31 +0300
Message-ID: 
 <CAFCfRH6XV9h6Li9P+aArfstku18ipf=xRBK-tMvcAOnCd8vutA@mail.gmail.com>
Subject: Re: ivy buildlist producing incorrect order of dependencies
To: ivy-user@ant.apache.org
Content-Type: multipart/alternative; boundary=001a11c37f14dd5b190503ade96f
X-Virus-Checked: Checked by ClamAV on apache.org

--001a11c37f14dd5b190503ade96f
Content-Type: text/plain; charset=UTF-8

Thank you, Zac ! Indeed, I managed to track down the problem: once I set
the actual name of the module, everything works fine.

For example I had to change from:



*info organisation="com.test.ivy" module="${ant.project.name
<http://ant.project.name>}"        revision="${test.release}"
status="${proj.status}"/>*

to:


*<info organisation="com.test.ivy" module="UtilPrj"
revision="${test.release}" status="${proj.status}"/>*

It seems this is a bug in the buildlist ivy tag, as the ${ant.project.name}
is correctly replaced in every other situation.

Well, for the moment I'll have to live with duplicating the module name in
the ivy.xml file.



On Mon, Sep 22, 2014 at 10:23 PM, Zac Jacobson <pie.fed@gmail.com> wrote:

> Oh I see what you mean.
>
> Well, if it's not able to establish dependencies, perhaps it doesn't take
> your complex ant file included into account.
>
> In your example, I put explicit values in the ivy file for UtilPrj and it
> seems to come back in the expected order.
>
> <info organisation="com.test.ivy" module="UtilPrj"
> revision="${test.release}"
> status="${proj.status}"/>
>
> On Mon, Sep 22, 2014 at 11:37 AM, Zac Jacobson <pie.fed@gmail.com> wrote:
>
> > Your ant script is building projects in alphabetical order, which happens
> > to not match your ivy dependency order. So PrjDependingOnUtilPrj is built
> > first, but it can't find a UtilPrj because that project hasn't been
> > built/published yet.
> >
> > You should give your master ant file the explicit order to build/publish
> > things, if that's what you want to do.
> >
> > On Mon, Sep 22, 2014 at 2:07 AM, Ionut Scutaru <ionut.scutaru@gmail.com>
> > wrote:
> >
> >> Hi,
> >>
> >> I'm using Ivy 2.2.0 and Ant 1.9.2 and I'm currently facing a problem
> >> related to ivy:buildlist: it generates the list of dependencies in the
> >> project in the wrong order.
> >>
> >> I'm attaching a configuration that shows the problem that I'm facing.
> >>
> >> I'm running the build.xml located in the deploymentUtilities/ant.new
> >> folder and I see this error in the console:
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> *[ivy:resolve]
> >> ::::::::::::::::::::::::::::::::::::::::::::::[ivy:resolve]
> >> ::          UNRESOLVED DEPENDENCIES         ::[ivy:resolve]
> >> ::::::::::::::::::::::::::::::::::::::::::::::[ivy:resolve]           ::
> >> com.test.ivy#UtilPrj;1.0.0: not found[ivy:resolve]
> >>
> ::::::::::::::::::::::::::::::::::::::::::::::[ivy:resolve][ivy:resolve][ivy:resolve]
> >> :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS*
> >>
> >> Could anybody help me ? I really don't understand why the order is not
> >> the correct one.
> >>
> >> Thank you !
> >>
> >
> >
>

--001a11c37f14dd5b190503ade96f--