Return-Path: X-Original-To: apmail-ant-ivy-user-archive@www.apache.org Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8BBC99DBA for ; Mon, 20 Feb 2012 00:46:37 +0000 (UTC) Received: (qmail 37116 invoked by uid 500); 20 Feb 2012 00:46:37 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 37089 invoked by uid 500); 20 Feb 2012 00:46:37 -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 37080 invoked by uid 99); 20 Feb 2012 00:46:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Feb 2012 00:46:37 +0000 X-ASF-Spam-Status: No, hits=3.1 required=5.0 tests=FSL_RCVD_USER,HK_RANDOM_ENVFROM,HK_RANDOM_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sugarbzzzz@gmail.com designates 209.85.214.173 as permitted sender) Received: from [209.85.214.173] (HELO mail-tul01m020-f173.google.com) (209.85.214.173) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Feb 2012 00:46:29 +0000 Received: by obbup16 with SMTP id up16so7443493obb.4 for ; Sun, 19 Feb 2012 16:46:08 -0800 (PST) Received-SPF: pass (google.com: domain of sugarbzzzz@gmail.com designates 10.60.29.34 as permitted sender) client-ip=10.60.29.34; Authentication-Results: mr.google.com; spf=pass (google.com: domain of sugarbzzzz@gmail.com designates 10.60.29.34 as permitted sender) smtp.mail=sugarbzzzz@gmail.com; dkim=pass header.i=sugarbzzzz@gmail.com Received: from mr.google.com ([10.60.29.34]) by 10.60.29.34 with SMTP id g2mr8200503oeh.72.1329698768510 (num_hops = 1); Sun, 19 Feb 2012 16:46:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=RDdmPnYdxMOZlV7NRUh3Fy6w7mmYrAgMYCVIV4shEmI=; b=RweJ2T+Uro20MBMNPQVgmjnJ43wdmfZfK/oqWF26lI/skABt9e+p5J2JXWAR5MA1Ap x+GNX0zyK/kL6+1OV0RYVHLieAxG++BobbDJp4/sZkKaju+e4drrf99mNSRq+C0O1rN0 TfOk8y9j72B/GTWhwRuKvmtbh+XE2923GOvTg= MIME-Version: 1.0 Received: by 10.60.29.34 with SMTP id g2mr7017664oeh.72.1329698768467; Sun, 19 Feb 2012 16:46:08 -0800 (PST) Received: by 10.60.133.137 with HTTP; Sun, 19 Feb 2012 16:46:08 -0800 (PST) Date: Sun, 19 Feb 2012 18:46:08 -0600 Message-ID: Subject: avoiding cleaning the cache all the time From: Sugar Bzzz To: ivy-user@ant.apache.org Content-Type: multipart/alternative; boundary=e89a8ff1c574c0b75e04b95a9e86 X-Virus-Checked: Checked by ClamAV on apache.org --e89a8ff1c574c0b75e04b95a9e86 Content-Type: text/plain; charset=ISO-8859-1 Hello, I have two projects: LibX and AppY, where AppY depends on LibX. I would like to establish the following workflow with Ivy: 1) make some changes to LibX 2) rebuild and publish the modified LibX using Ant+Ivy 3) rebuild AppY using the modified LibX 4) repeat (goto 1) This works the first time around (with a clean cache) but it doesn't work a second time. When I rebuild AppY a second time around, it uses a cached LibX from the first iteration of this workflow. The only way I can get the latest LibX when building AppY after publishing LibX once already, is to clean the Ivy cache and start over; but this takes a long time since all of the dependencies of LibX need to be redownloaded. I want AppY to use the latest LibY that I've built. How can I achieve this without having to clean the Ivy cache every time I modify LibX? Thanks. Here is how I have Ant and Ivy setup: in build.xml of LibX: in ivy.xml of LibX: <... several dependencies here ...> in build.xml of AppY: in ivy.xml of AppY: --e89a8ff1c574c0b75e04b95a9e86--