Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 48117 invoked from network); 3 Nov 2010 13:11:48 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 3 Nov 2010 13:11:48 -0000 Received: (qmail 58576 invoked by uid 500); 3 Nov 2010 13:12:19 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 58276 invoked by uid 500); 3 Nov 2010 13:12:17 -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 58265 invoked by uid 99); 3 Nov 2010 13:12:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Nov 2010 13:12:16 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of cblistserv@gmail.com designates 209.85.215.45 as permitted sender) Received: from [209.85.215.45] (HELO mail-ew0-f45.google.com) (209.85.215.45) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Nov 2010 13:12:09 +0000 Received: by ewy3 with SMTP id 3so238038ewy.4 for ; Wed, 03 Nov 2010 06:11:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=j/+X6MaXI+BlKecDs/7bXGAgqCCh1PV+fZrbZYGClWA=; b=XkdgSuu3ZMSucwyZJtixLKv2okcmK5hdoWxR692Cmz41hTsaQW8IojoShQMg2tk+Ow z7dWNfuM3FNqEADa3uuwnV6FaMBbyRdQ8Kpe/hIpn4Jm4G5JBo4FKTyXj0zbCR2y92kM ngt7P7CJSQ1PCj4WHVJ4JVP+OeCZMkDia/Lb4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=hFnNf3YK9Rf652SsdIX5Dz+h5JaISdiLO+pKhz5PUiB9tJTRvCSuDP5iwZQWF2VGU/ XQojJYHuKiGJsOo9OpWymTKk/vUE4qDE5Lmq3fvuc+Nqx85uX3yLvkB6kuduZWjhOb6K 442U+pSUptz01rMkcM2zfRLpgTdHI/xOcDwdM= MIME-Version: 1.0 Received: by 10.213.112.204 with SMTP id x12mr499389ebp.81.1288789907985; Wed, 03 Nov 2010 06:11:47 -0700 (PDT) Received: by 10.213.112.145 with HTTP; Wed, 3 Nov 2010 06:11:47 -0700 (PDT) Date: Wed, 3 Nov 2010 09:11:47 -0400 Message-ID: Subject: Setting transitive=true on one dependency results in transitive resolution for all children From: Carlton Brown To: ivy-user@ant.apache.org Content-Type: multipart/alternative; boundary=0015174bed66a7d49f049425c806 --0015174bed66a7d49f049425c806 Content-Type: text/plain; charset=ISO-8859-1 I have some modules that have dependency relationships specified like this: B depends on A, transitive=false A depends on log4j, transitive=false When I change the B=>A dependency to 'transitive=true', now the B=>log4j dependency also resolves transitively, even though transitive=false for that module. This is not expected and definitely not desired... does anyone have an idea why this may be happening? Module B's ivy.xml: Module A's ivy.xml: --0015174bed66a7d49f049425c806--