From ivy-user-return-2348-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org Mon Jan 21 23:24:06 2008 Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 53180 invoked from network); 21 Jan 2008 23:24:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Jan 2008 23:24:06 -0000 Received: (qmail 89060 invoked by uid 500); 21 Jan 2008 23:23:55 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 89033 invoked by uid 500); 21 Jan 2008 23:23:55 -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 89024 invoked by uid 99); 21 Jan 2008 23:23:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Jan 2008 15:23:55 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of esumerfd@gmail.com designates 66.249.82.234 as permitted sender) Received: from [66.249.82.234] (HELO wx-out-0506.google.com) (66.249.82.234) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Jan 2008 23:23:30 +0000 Received: by wx-out-0506.google.com with SMTP id h30so3723702wxd.10 for ; Mon, 21 Jan 2008 15:23:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to:sender:to:subject:mime-version:content-type:x-google-sender-auth; bh=78e8doX9Ys6J07T1qUEqiACenRnE9Xm//BQTh1ctVhU=; b=C70au3OS45nozKrMQntRdPdTzUP0fAU44aoajF0cnFtCyTumi2lMAUVMCtHZxyiLHARITpKCF/1aPLlJ2z21TEAOKWrCt5mXah0F4wyEQefFiTRVdt+9UOwvzPtIvfm8G14DyZUDC/8uyQxh/QfttzsZ7zk+XVp43CWDRgDN0iw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:sender:to:subject:mime-version:content-type:x-google-sender-auth; b=C0MiJtsdn9RUyBphIp8qYJAGwouWFcuWxeE+lRlgu31MhGLObkL2IDHhTnwmWxCRyGYlTooEnnJTe6BiKM7fXOeUonXaWajWSew7SThDxWcNtxAevInMuY5VO8JauHUM9snrWJomIPZ0ePuowr6+CXG2DGxAGAzEt2m4+HVMX1E= Received: by 10.70.37.12 with SMTP id k12mr4897112wxk.70.1200957815382; Mon, 21 Jan 2008 15:23:35 -0800 (PST) Received: by 10.70.54.4 with HTTP; Mon, 21 Jan 2008 15:23:35 -0800 (PST) Message-ID: <6a216ba20801211523h1ad1ad34j256cb0eb4dd3effa@mail.gmail.com> Date: Mon, 21 Jan 2008 18:23:35 -0500 From: "Edward Sumerfield" Reply-To: esumerfd@bitbashers.org Sender: esumerfd@gmail.com To: IvyUsers Subject: Publish to local vs Retrieved from cache MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_13751_24126905.1200957815389" X-Google-Sender-Auth: 7dcaaeeb18a6adf7 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_13751_24126905.1200957815389 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I have just started publishing jars from one project and making then dependents to others. This works well except there is some kind of caching issue. The publish appears to place the jars in .ivy2/local to be picked up and copied to .ivy2/cache. Now when a new jar is published to local it is not updated in cache? What is the best way to handle this? -- Ed ------=_Part_13751_24126905.1200957815389--