Return-Path: 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 1F76474CE for ; Wed, 31 Aug 2011 13:54:47 +0000 (UTC) Received: (qmail 65316 invoked by uid 500); 31 Aug 2011 13:54:46 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 65222 invoked by uid 500); 31 Aug 2011 13:54:46 -0000 Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@ant.apache.org Delivered-To: mailing list ivy-user@ant.apache.org Received: (qmail 65214 invoked by uid 99); 31 Aug 2011 13:54:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Aug 2011 13:54:45 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of nzipsi@gmail.com designates 209.85.212.45 as permitted sender) Received: from [209.85.212.45] (HELO mail-vw0-f45.google.com) (209.85.212.45) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Aug 2011 13:54:39 +0000 Received: by vws17 with SMTP id 17so606704vws.4 for ; Wed, 31 Aug 2011 06:54:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=fxru3NPBZe8keJW604VXRXUf1V48BzKYnQoKyJ7jPDw=; b=kijkfu6cGFBcgUPzHR7gexCOmFOgwfJ7TZ2RBUHw2OF4bCYbFH7Q+Wg58Ipyu7B9Uc 4XcvVqz84nshLwARwJ50lFTa6NBCPwqbKFqy6MBhn9H0SMV9gXfS0kcucnD4Bv/2jeJf 6pQUeROcvTZ12xvnKYAs73NftFgmTpYHWqq0U= MIME-Version: 1.0 Received: by 10.52.71.239 with SMTP id y15mr378708vdu.213.1314798858389; Wed, 31 Aug 2011 06:54:18 -0700 (PDT) Received: by 10.52.111.201 with HTTP; Wed, 31 Aug 2011 06:54:18 -0700 (PDT) In-Reply-To: References: Date: Thu, 1 Sep 2011 01:54:18 +1200 Message-ID: Subject: Re: Transitive repreport? From: Andrew Thorburn To: ivy-user@ant.apache.org Content-Type: text/plain; charset=UTF-8 You should just be able to use the report task, I think: http://ant.apache.org/ivy/history/latest-milestone/use/report.html That should, I believe, traverse the whole graph, though the output might not be exactly what you're looking for. If it's not, it shouldn't be too hard to use the XML to generate a report that fits your requirement (The report task supports providing a custom XSL transform). - Andrew On Thu, Sep 1, 2011 at 1:00 AM, Anders Jacobsson wrote: > Hi! > > I am working with a product that involves cryptography and thus we are > subject to trade compliance. I need to figure out a way to easily spot which > 3PPs our modules (of which we have a lot) use so that we can cross-reference > those against a list of 3PPs that include cryptography. > > My thought was to use the repreport task but it does not seem to be able to > traverse the dependency chain for all configurations all the way down. Let > me give an example: > > Module A depends on B through the X configuration and module B depends on C > and D through the Y and Z configurations, respectively. If I run repreport > on module A, the report would only include modules A and B. I would like it > to "restart" on module B and look at all configurations and not only X. > > Is this possible to achieve with repreport or does it require a custom task? > > Cheers, > Anders >