Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 22826 invoked from network); 19 May 2009 15:15:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 19 May 2009 15:15:09 -0000 Received: (qmail 64005 invoked by uid 500); 19 May 2009 15:15:09 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 63945 invoked by uid 500); 19 May 2009 15:15:09 -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 63935 invoked by uid 99); 19 May 2009 15:15:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 May 2009 15:15:09 +0000 X-ASF-Spam-Status: No, hits=-1.0 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [65.55.88.15] (HELO TX2EHSOBE009.bigfish.com) (65.55.88.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 May 2009 15:14:58 +0000 Received: from mail93-tx2-R.bigfish.com (10.9.14.246) by TX2EHSOBE009.bigfish.com (10.9.40.29) with Microsoft SMTP Server id 8.1.340.0; Tue, 19 May 2009 15:14:36 +0000 Received: from mail93-tx2 (localhost.localdomain [127.0.0.1]) by mail93-tx2-R.bigfish.com (Postfix) with ESMTP id B1BDEE68B45 for ; Tue, 19 May 2009 15:14:36 +0000 (UTC) X-BigFish: VPS-21(z5edJz542N1432R1805Mzz1202hzzz2dh6bh43j) X-FB-SS: 5,13, Received: by mail93-tx2 (MessageSwitch) id 1242746070457064_18560; Tue, 19 May 2009 15:14:30 +0000 (UCT) Received: from USEX02.gsc.zz (unknown [12.3.88.212]) by mail93-tx2.bigfish.com (Postfix) with ESMTP id 1E7AA9B005C for ; Tue, 19 May 2009 15:14:30 +0000 (UTC) Received: from webmail.gsc.zz ([172.18.40.39]) by USEX02.gsc.zz with Microsoft SMTPSVC(6.0.3790.3959); Tue, 19 May 2009 11:14:04 -0400 Received: from atex01.gsc.zz ([192.168.225.11]) by webmail.gsc.zz with Microsoft SMTPSVC(6.0.3790.3959); Tue, 19 May 2009 11:14:04 -0400 Received: from atex01.gsc.zz ([192.168.225.11]) by atex01.gsc.zz ([192.168.225.11]) with mapi; Tue, 19 May 2009 17:14:02 +0200 From: "Bieringer, Dominik" To: "ivy-user@ant.apache.org" Date: Tue, 19 May 2009 17:14:00 +0200 Subject: RE: Cache not update Thread-Topic: Cache not update Thread-Index: AcnYkq5Zz1uOzOwITTeUj4Ghgak2dQAAaGCg Message-ID: <6CE22786EBF2FB4DA38C65DA76CA60D61F0D0D25EA@atex01.gsc.zz> References: <8A7677FA69ECE846AFAAF747AFDA7FE6157967846C@SI-MBX03.de.bosch.com> <20090519151616.GU11304@dusk.harfang.homelinux.org> In-Reply-To: <20090519151616.GU11304@dusk.harfang.homelinux.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 19 May 2009 15:14:04.0079 (UTC) FILETIME=[724713F0:01C9D894] X-Virus-Checked: Checked by ClamAV on apache.org I had the same problem. I got it resolved by also updating the publication = timestamp in the ivy.xml file ;). -----Original Message----- From: Gilles Sadowski [mailto:gilles@harfang.homelinux.org]=20 Sent: Tuesday, May 19, 2009 17:16 To: ivy-user@ant.apache.org Subject: Re: Cache not update Hi. >=20 > I have a problem when retrieving artifacts from a filesystem repository. = Ivy is always using the file from the cache even if there is a more recent = version in the repository. I tried several ways to force Ivy to update the = cache, but none of them have any effect. Therefore I assume that this is a = bug in ivy. What I tried so far: >=20 > - changing=3Dtrue on the dependency in ivy.xml > - checkModified=3Dtrue on the filesystem resolver in ivysettings.xml > - changingPattern=3D".*" on the filesystem resolver >=20 > [...] > > As a workaround, I am deleting the cache before every resolve. I have posted a message reporting this exact same problem. I had tried the same things, and currently use the same inefficient or error-prone workaround. Needless to say that I'm also very interested in having this sorted out (whether bug or feature requiring some appropriate config). Gilles