Return-Path: X-Original-To: apmail-ant-dev-archive@www.apache.org Delivered-To: apmail-ant-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 55F6B101D6 for ; Tue, 24 Dec 2013 00:13:07 +0000 (UTC) Received: (qmail 84963 invoked by uid 500); 24 Dec 2013 00:13:07 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 84914 invoked by uid 500); 24 Dec 2013 00:13:07 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 84906 invoked by uid 99); 24 Dec 2013 00:13:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Dec 2013 00:13:07 +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 charles@dyfis.net designates 209.85.213.178 as permitted sender) Received: from [209.85.213.178] (HELO mail-ig0-f178.google.com) (209.85.213.178) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Dec 2013 00:13:00 +0000 Received: by mail-ig0-f178.google.com with SMTP id ut6so14460522igb.5 for ; Mon, 23 Dec 2013 16:12:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dyfis.net; s=google; h=mime-version:date:message-id:subject:from:to:content-type; bh=72sB3mrDI9c/V7ZR8BthOSsD4/Xdy+bECVwM20arV6U=; b=bbqHsQZG4ubyXHIwuzFJfD4k6qTb626/D9faP+u1aX1xMgYesw0t1G/2zUtpMsqhfl YKyKYPn6p1zy7+KF0iGDF58h6Cro+m5eBS1ZQBXPLnEMPpregB6fMeE2GSvIaSXy2Zzm BfH1It2vti45KhbPkf1Z0XyMtHe06ESF8hSNU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=72sB3mrDI9c/V7ZR8BthOSsD4/Xdy+bECVwM20arV6U=; b=Xqb51ESacDXLFVaVrShGGJTe6qwp+oHCT13A0R4r08kdisbGGQPQCYQs6aPBQsYGpI dtDcsP+7oJq2vVtp6QTwW9G2Jxhe2cGZlr9ox9ciuR4FVZSXYuDzdt6MTqez0AIpuUCD C+5qlFMIV2K3oUxzf/MVsMFMyFL4r57KhJ9PfepthV8HiqnmWyssS0SzrkV8S2RhJ+Vp s9ukK2kIDOkq9E7z2pPywMVVjq8x4JvlLIGCjqBq6aC7GcFEceYb65Ou5CxDu20KWEmG nwxpT8OyAA9rGKuZdRL8Mti57V0GZnseEUdwFVO1OvR/bJ+LMqSJPZhlN4csRk6tnP2M gDqw== X-Gm-Message-State: ALoCoQmurXAYbbCZQLfx6S/AYYM3cuPJaCPaR7AOJgvajddTOXuIkrBwAbUkBfqqC/XfZczPnkv8 MIME-Version: 1.0 X-Received: by 10.50.40.102 with SMTP id w6mr23866234igk.20.1387843959348; Mon, 23 Dec 2013 16:12:39 -0800 (PST) Received: by 10.64.8.71 with HTTP; Mon, 23 Dec 2013 16:12:39 -0800 (PST) Date: Mon, 23 Dec 2013 18:12:39 -0600 Message-ID: Subject: IVY-1455: effects of override tag escaping definition scope From: Charles Duffy To: Ant Developers List Content-Type: multipart/alternative; boundary=089e0112c7fe33772004ee3c9af9 X-Virus-Checked: Checked by ClamAV on apache.org --089e0112c7fe33772004ee3c9af9 Content-Type: text/plain; charset=UTF-8 Howdy, all -- I have a reproducer for an issue similar to IVY-1333 ("impossible to get artifacts when data has not been loaded") which demonstrates some surprising behavior, and would appreciate feedback from folks more familiar with the ResolveEngine's internals: An tag in a transitive dependency is impacting the overall resolution, even when no child of that dependency matches the pattern described by the tag in question. The tree looks as follows: reproducer/top-level |- conflict/conflict==1 [conf="with-direct-dep->default"] |- reproducer/phase-one==1 [conf="master->*"] | |- conflict/conflict==2 | |- reproducer/phase-two==1 | | |- empty-module/empty-module==1 | | |- [override:conflict/conflict==1] Because phase-two has no children with a dependency on conflict/conflict (its only child being empty-module), it is entirely surprising to me that its override tag has any effect whatsoever. (However, removing the dependency on empty-module *also* circumvents the bug). The top-level reproducer has two confs descended from master, "with-direct-dep" and "without-direct-dep". In both, conflict/conflict is resolved to version 2, but in the latter, conflict/conflict==1 is not loaded at all. Only when both of these confs are invoked within a single ivy:resolve task does the issue in question trigger. Could I ask for some pointers in the right direction to get a better handle on what might be going on here? The reproducer in question is attached to IVY-1455 as a zip file. Many thanks, -- Charles --089e0112c7fe33772004ee3c9af9--