From ivy-user-return-6759-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org Tue May 04 21:15:27 2010 Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 34150 invoked from network); 4 May 2010 21:15:27 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 4 May 2010 21:15:27 -0000 Received: (qmail 85164 invoked by uid 500); 4 May 2010 21:15:26 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 85131 invoked by uid 500); 4 May 2010 21:15:26 -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 85123 invoked by uid 99); 4 May 2010 21:15:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 May 2010 21:15:26 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of archie.cobbs@gmail.com designates 74.125.82.173 as permitted sender) Received: from [74.125.82.173] (HELO mail-wy0-f173.google.com) (74.125.82.173) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 May 2010 21:15:21 +0000 Received: by wyj26 with SMTP id 26so2607866wyj.4 for ; Tue, 04 May 2010 14:14:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type; bh=Eq56OQYkVaIzysxXZIt/+w0G3a4dqC2+2KNwC/96AAM=; b=InqP6g8StsntETbhJ7hTh1tJYTaZqzZMlAQv799AxkcWdCOLWLS4IxSamU5q4s0mGL EcU/BygYyx0QoowY/la6uvNKCkvLL4MSD31+nLZytFrD91Pz3n1j7fLObXPFTCVLMiYN Jw3qQl3VFQ+aqTEQyDzEnE+fTlXlRXwqAlRCE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=dtcIUZfnp0i2Pj1zX5K5ghC5RYb2DhQojRBlfLQKqPIUgT3RVU/XIECXDIzGe6mtUr kHemB7hefkblUMCnIsW6Wq1IWLSFjNW6uKTrjmDFp36MJgCrrjRP8C/da3ofa0LbrOyP OvPibNPgJ+AagGQqyzSVvciRKEZdpYh4zeuWQ= Received: by 10.216.88.11 with SMTP id z11mr3699933wee.116.1273007699221; Tue, 04 May 2010 14:14:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.233.78 with HTTP; Tue, 4 May 2010 14:14:39 -0700 (PDT) In-Reply-To: <28453055.post@talk.nabble.com> References: <28450261.post@talk.nabble.com> <28453055.post@talk.nabble.com> From: Archie Cobbs Date: Tue, 4 May 2010 16:14:39 -0500 Message-ID: Subject: Re: conf mapping documentation contradicts itself To: ivy-user@ant.apache.org Content-Type: multipart/alternative; boundary=0016e6d9a388b55bb70485cb33d2 --0016e6d9a388b55bb70485cb33d2 Content-Type: text/plain; charset=ISO-8859-1 On Tue, May 4, 2010 at 4:01 PM, mjparme wrote: > The reason the current verbiage of "master configuration (i.e. the > configuration of the module defining the dependency)" is confusing because > it reads like it is talking about the ivy file that defines the dependency. > Whereas the first sentence defines master configuration as the ivy file of > the current module. > Seems like there's still confusion about what the docs intended to mean... The ivy file defining the dependency *is* the ivy file of the current module. Here the word "dependency" is referring to a relationship between two modules. So there are three things being defined here: two modules and a dependency. The dependency is defined inside the "master" module's ivy.xml file. The module being depended on is of course defined by it's ivy.xml file (i.e., the other ivy.xml file). So modules "know" what they depend on, but modules don't "know" who depends on them. -Archie -- Archie L. Cobbs --0016e6d9a388b55bb70485cb33d2--