Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 87456 invoked from network); 12 Nov 2008 23:07:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Nov 2008 23:07:38 -0000 Received: (qmail 78172 invoked by uid 500); 12 Nov 2008 23:07:44 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 78144 invoked by uid 500); 12 Nov 2008 23:07:44 -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 78133 invoked by uid 99); 12 Nov 2008 23:07:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Nov 2008 15:07:44 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [68.142.200.151] (HELO web30808.mail.mud.yahoo.com) (68.142.200.151) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 12 Nov 2008 23:06:24 +0000 Received: (qmail 71152 invoked by uid 60001); 12 Nov 2008 23:06:05 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=SZswikGWdhFR1bvzrHk5YaCalbaQ7dHqZARe1wcwDEo10i6iacua884A0nMStpgWDuVGoGiEdrl+5rGscJCsDutsv5U06JeVz5CHftktwiCcHbjgue0xITdz1wabcr8XriiNGNvSPXq6C6npv43OtKX0+eigawFNY4IvDdX9eXw=; X-YMail-OSG: l0qs5VEVM1nYszeNpCfvhU4DtgVRJ1rI7qB_jgLmlGO2.rjpeXOvW6Ik1k3c3EBcRAf42PWlzr9J6RVdQmixMLvpAzBVhk2aI80pjBmWprwM9yLqWAzPV0tDpX46wB3jLLfkCro4zqpAWtFlM5ccWcJlFDovljBmRYpugX4Wfoi1n1BeXr1bETfzozm0 Received: from [81.240.160.121] by web30808.mail.mud.yahoo.com via HTTP; Wed, 12 Nov 2008 15:06:04 PST X-Mailer: YahooMailRC/1155.20 YahooMailWebService/0.7.260.1 References: <34721A41A7BCF54ABC3B116219A8C1C204F8608E24@NP1EXCH012.corp.halliburton.com> Date: Wed, 12 Nov 2008 15:06:04 -0800 (PST) From: Maarten Coene Subject: Re: Ivy can mutate Ant properties? What? To: ivy-user@ant.apache.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <970497.70508.qm@web30808.mail.mud.yahoo.com> X-Virus-Checked: Checked by ClamAV on apache.org Hi Carlton, Ivy is indeed a very powerfull tool, it can even change Ant properties ... ;-) Just kidding and you are probably right, we should not modify properties that were set outside Ivy. However, I think it could be a difficult excercise to modify the current behaviour because the Ivy Ant tasks use some properties to pass state (like resolve information for instance). If Ivy cannot set/update these properties correctly, unpredictable results can happen. And as you already know, you can create a JIRA ticket if you want to see this changed in some future release... Maarten ----- Original Message ---- From: "Brown, Carlton" To: ivy-user@ant.apache.org Sent: Wednesday, November 12, 2008 7:14:08 PM Subject: RE: Ivy can mutate Ant properties? What? The ivy task mutated an Ant property in the Ant script, not in a settings file. Is that still expected behavior? It's true that the property coincided with a commonly used Ivy property, but I would not expect Ivy to mutate any Ant property that was not set by Ivy itself. -----Original Message----- From: Shawn Castrianni [mailto:Shawn.Castrianni@halliburton.com] Sent: Wednesday, November 12, 2008 1:02 PM To: 'ivy-user@ant.apache.org' Subject: RE: Ivy can mutate Ant properties? What? Yes, this is default behavior. IVY settings files can have properties with the option to alter pre-existing properties. The option is in the "override" attribute. If you set it to false, then you will not mutate any ANT pre-existing properties. --- Shawn Castrianni -----Original Message----- From: Brown, Carlton [mailto:Carlton.Brown@compucredit.com] Sent: Wednesday, November 12, 2008 11:57 AM To: ivy-user@ant.apache.org Subject: Ivy can mutate Ant properties? What? I was surprised today to observe that the ivy:info task can mutate Ant properties, which are supposedly immutable. In this snippet of Ant code, I hardcode some Ant properties. After a call to ivy:info, these properties have changed, which should not occur (as far as I understand). Can anyone explain what's going on here? This is the output: test-mutability: [echo] pre-info organization: foo.bar [echo] pre-info module: mutant [echo] pre-info revision: 9.8 [echo] pre-info status: beta [ivy:info] :: Ivy 2.0.0-rc1 - 20080916082609 :: http://ant.apache.org/ivy/ :: :: loading settings :: file = c:\allworkspaces\ebiz-1.6-rmtest\ivy-template\ivy-settings-common.xml [echo] post-info organization: com.mycompany.myorg [echo] post-info module: mymodule [echo] post-info revision: 3.0-dev1 [echo] post-info status: integration ----------------------------------------- ==================================================== This message contains PRIVILEGED and CONFIDENTIAL information that is intended only for use by the named recipient. If you are not the named recipient, any disclosure, dissemination, or action based on the contents of this message is prohibited. In such case please notify us and destroy and delete all copies of this transmission. Thank you. ====================================================