Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 64944 invoked from network); 4 May 2010 16:54:38 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 4 May 2010 16:54:38 -0000 Received: (qmail 1369 invoked by uid 500); 4 May 2010 16:54:38 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 1348 invoked by uid 500); 4 May 2010 16:54:38 -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 1340 invoked by uid 99); 4 May 2010 16:54:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 May 2010 16:54:38 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,SPF_HELO_PASS,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 May 2010 16:54:31 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1O9LNq-0000lu-9b for ivy-user@ant.apache.org; Tue, 04 May 2010 09:54:10 -0700 Message-ID: <28450261.post@talk.nabble.com> Date: Tue, 4 May 2010 09:54:10 -0700 (PDT) From: mjparme To: ivy-user@ant.apache.org Subject: conf mapping documentation contradicts itself MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: mjparmeley@west.com X-Virus-Checked: Checked by ClamAV on apache.org The documentation regarding the syntax of the -> operator for conf mapping is unnecessarily confusing and in fact contradicts itself. IMHO, it needs to better define what it means by the master configuration and what is the dependency configuration. Documentation is located here and the relevent section is Configuration Mapping: http://ant.apache.org/ivy/history/latest-milestone/ivyfile/dependency.html First sentence reads: "This mapping indicates which configurations of the dependency are required in which configurations of the current module, also called master configurations." This suggests that the master configuration is the "configuration of the current module" which I assume is the ivy module file I am currently looking at. However, later it says: "A good way to remember which side is for the master configuration (i.e. the configuration of the module defining the dependency) and which side is for the dependency configuration is to read the '->' as 'depends on'." Now this suggests that the master configuration is the configuration of the module of the artifact I am declaring as a dependency. This totally contradicts the first sentence of the section and this documentation is totally ambiguous. Could someone clarify this for me? Is it: configuration of module file I am currently looking at -> (depends on) configuration from artificat's module file or configuration from artifact's module file -> (depends on) configuration of module file I am currently looking at The first option makes more sense to me, so that is what I think it is. -- View this message in context: http://old.nabble.com/conf-mapping-documentation-contradicts-itself-tp28450261p28450261.html Sent from the ivy-user mailing list archive at Nabble.com.