Return-Path: 
 <ivy-user-return-3924-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-ivy-user-archive@www.apache.org
Received: (qmail 47767 invoked from network); 18 Sep 2008 17:10:21 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 18 Sep 2008 17:10:21 -0000
Received: (qmail 16055 invoked by uid 500); 18 Sep 2008 17:10:17 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 16023 invoked by uid 500); 18 Sep 2008 17:10:17 -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 16012 invoked by uid 99); 18 Sep 2008 17:10:17 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Sep 2008 10:10:17 -0700
X-ASF-Spam-Status: No, hits=2.6 required=10.0
	tests=SPF_PASS,WHOIS_MONIKER_PRIV
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of mark.melvin@gmail.com
 designates 209.85.217.18 as permitted sender)
Received: from [209.85.217.18] (HELO mail-gx0-f18.google.com) (209.85.217.18)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Sep 2008 17:09:19 +0000
Received: by gxk11 with SMTP id 11so22653939gxk.4
        for <ivy-user@ant.apache.org>; Thu, 18 Sep 2008 10:09:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to
         :subject:mime-version:content-type:content-transfer-encoding
         :content-disposition;
        bh=hREwqk+yGOarc6Adv1MvF2H6loX2wGuqIkDIOmMxX08=;
        b=a9GfOWU06nCT6TLh31Xpwh22TY9Igxtc5weghWyB+enpujetCr5gefuu34NyhSZYBi
         s4ZBQJ5hmG8iFGJSf3aK3tVeu1J8SP3qtSfH9Rulh5+ZlMTARQ5LKO+SRYOrlwKvnn3E
         dQJc6WxhmpDoTrUYUh2VS4fBwHGNw/jDhMgDo=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:mime-version:content-type
         :content-transfer-encoding:content-disposition;
        b=x0btJ9Qs232anaT4mIXRrMB0ywZzhHyDTFKYxcZZs6lCiPKpbTbGootREzezWVLMC+
         uG4u2Z8Olt6lmu8LZzMw9mjjYayETeffQiOkO0ufTXHPbNZuabSgM8sKWe+IYBaBpKpI
         x/UUZLOClEHwhXTUe3bw1WpLAxHekSeyOoXFE=
Received: by 10.142.207.8 with SMTP id e8mr1512970wfg.110.1221757790253;
        Thu, 18 Sep 2008 10:09:50 -0700 (PDT)
Received: by 10.142.203.16 with HTTP; Thu, 18 Sep 2008 10:09:50 -0700 (PDT)
Message-ID: <f2cc73f90809181009y286f36bet8f00d9d9f95b20d8@mail.gmail.com>
Date: Thu, 18 Sep 2008 13:09:50 -0400
From: "Mark Melvin" <mark.melvin@gmail.com>
To: ivy-user@ant.apache.org
Subject: How To Get Module Dependency List
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Checked: Checked by ClamAV on apache.org

Hi,

Someone please correct me if I am wrong - but I don't see any way to
simply get a reference to an ordered list of dependencies (using Ant).
 I see there is the ivy:buildlist task, but this assumes you have all
of your dependencies available in a directory somewhere.  I would like
to get this information just by doing a resolve.  I tried using this
task with the cache, like so:

    <ivy:cachefileset organisation="my.org" module="myModule"
inline="true" setid="deps.fileset"/>
    <ivy:buildlist reference="build-path" skipbuildwithoutivy="true">
        <fileset refid="deps.fileset"/>
    </ivy:buildlist>

But this finds nothing because the path to the ivy.xml files is
non-standard in the cache.  Fine, I change it like so:

    <ivy:buildlist reference="build-path" skipbuildwithoutivy="true"
ivyfilepath="../ivys/ivy.xml">
        <fileset refid="deps.fileset"/>
    </ivy:buildlist>

But that isn't going to work either - because the ivy files are stored
in the cache with the version number encoded in the filename.  And it
looks like the 'ivyfilepath' attribute does not accept any sort of
patterns.  I can get it to work if I hard-code the versioned filename
in the cache into the 'ivyfilepath' attribute - but that obviously is
not a solution moving forward.

So - perhaps I should explain what I am trying to do.  I just want to
get an ordered list of module names according to the transitive
dependencies.  This should be doable as the information is all there
after a resolve.  So if A depends on B depends on C, I just want to
get back "A, B, C".  The reason I want this is if I want to build A, I
want to walk the dependencies and trigger remote project builds in the
correct order (C, then B, then A).

Short of actually parsing the ivy files directly in the cache - is
there any way to do this?  This seems like a relatively basic thing to
do - but I don't see an easy way to do it.  Hopefully I am just
missing something obvious.

Thanks,
Mark.