Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 75293 invoked from network); 23 Jan 2008 22:52:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Jan 2008 22:52:22 -0000 Received: (qmail 85313 invoked by uid 500); 23 Jan 2008 22:52:12 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 85293 invoked by uid 500); 23 Jan 2008 22:52:12 -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 85280 invoked by uid 99); 23 Jan 2008 22:52:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Jan 2008 14:52:12 -0800 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.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; Wed, 23 Jan 2008 22:51:46 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1JHoRj-0003NQ-6y for ivy-user@ant.apache.org; Wed, 23 Jan 2008 14:51:51 -0800 Message-ID: <15054739.post@talk.nabble.com> Date: Wed, 23 Jan 2008 14:51:51 -0800 (PST) From: limbicsystem To: ivy-user@ant.apache.org Subject: "extra" attributes lost when dependencies are placed into cache MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: limbicsystem@gmail.com X-Virus-Checked: Checked by ClamAV on apache.org Hi, I'm making use of the "extra" attributes in in order to lay out staging directories for my artifacts. For example, I have a project that generates an ear file. It needs to place its dependencies in particular subdirs in the ear; some dependencies go in "APP-INF/lib", others go in "services". I accomplish this by setting a target.dir attribute in my ear project's dependencies, like so: Then I use ivy:retrieve to place my deps in the proper layout in my staging area: This works fine- I get a dir that looks like: staging.dir/runtime/APP-INF/lib/some-lib.jar staging.dir/runtime/services/another-lib.jar However, the "target.dir" attribute only seems to take effect when my ivy cache is empty- the initial retrieve works as expected, but subsequent retrieves seem to ignore target.dir, as if it were undefined for each dep. All my deps end up in staging.dir/runtime. If I do a cleancache, retrieve works properly again. I suspect that what is happening is when my dependencies' metadata gets placed into the Ivy cache, it does not have any target.dir attributes (this is logical, since these are defined in the ear project, not the dependencies' ivy.xmls). But when these artifacts are then found in the cache, "target.dir" is undefined, and this somehow causes its value to be disregarded in my ear's ivy.xml. I'm using Ivy 2.0.0-beta2-local-20080103173107. Thanks in advance for your time. -- View this message in context: http://www.nabble.com/%22extra%22-attributes-lost-when-dependencies-are-placed-into-cache-tp15054739p15054739.html Sent from the ivy-user mailing list archive at Nabble.com.