From ivy-user-return-5258-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org Tue May 12 13:25:19 2009 Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 34554 invoked from network); 12 May 2009 13:23:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 May 2009 13:23:18 -0000 Received: (qmail 60388 invoked by uid 500); 12 May 2009 13:23:18 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 60367 invoked by uid 500); 12 May 2009 13:23:18 -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 60357 invoked by uid 99); 12 May 2009 13:23:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 May 2009 13:23:18 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of joshua.tharp@gmail.com designates 209.85.200.169 as permitted sender) Received: from [209.85.200.169] (HELO wf-out-1314.google.com) (209.85.200.169) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 May 2009 13:23:08 +0000 Received: by wf-out-1314.google.com with SMTP id 28so2620502wfc.10 for ; Tue, 12 May 2009 06:22:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=yn+j7LzAOL1F3qAZ55pBHkdL6H+RGcF2mElaqnyT4+Y=; b=l3aTz+ZJAXEY4wB1iz8ShpJsDZWl9YpmRORNqXZ8F/FZcImDpxBbBzhE9lTMCccQdK m3Ac2IXzHiYlHkfft87AF0Nz3LohhQvW1LU0Vtjcmb4tCCgsknZ8b+Lb1Z0aFJyjFTn3 wENCQAihqH0TiViqZ4pN+H97R8kt/28Ji5n6Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=tYRWYmocHTWnicXdJSstkmeV9uOOSwYdQLQZrDHw5lda+bNAP+qASSlTN8kRBH6sH2 AHoiD+//JPgLw1eknr2Zj6q0lLA4ych8roxSWxwEoFsOUHFPm71njWZDIQ9VU1Nw46zD 1aLiLeDtwzE/to6zT12/yyrGdDUt6453GcYQM= MIME-Version: 1.0 Sender: joshua.tharp@gmail.com Received: by 10.142.191.5 with SMTP id o5mr3422540wff.53.1242134566803; Tue, 12 May 2009 06:22:46 -0700 (PDT) In-Reply-To: <20090512114525.GL11304@dusk.harfang.homelinux.org> References: <20090507144852.GH11304@dusk.harfang.homelinux.org> <20090512114525.GL11304@dusk.harfang.homelinux.org> Date: Tue, 12 May 2009 06:22:46 -0700 X-Google-Sender-Auth: 247486a78f3a070e Message-ID: Subject: Re: Changing revision does not update the cache From: Joshua Tharp To: ivy-user@ant.apache.org Content-Type: multipart/alternative; boundary=000e0cd28df29e1aa10469b6fd91 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd28df29e1aa10469b6fd91 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit This is what I have for my resolver While it shouldn't matter, you might try using the attribute "checkmodified" instead of "checkModified" and see if that fixes your parse error. On Tue, May 12, 2009 at 4:45 AM, Gilles Sadowski < gilles@harfang.homelinux.org> wrote: > Hi. > > No much reaction to that post: > > > Considering this excerpt of the ivy file for module "B": > > > > > rev="SNAPSHOT" > > changing="true"/> > > > > Module "A" is "publish"-ed to a (local "filesystem") repository. > > But when I "resolve", the cache is not updated with the latest version of > > the repository. Consequently, after a "retrieve" the classpath of "B" > still > > contains an old version of "A"! > > > > The documentation seems to imply that all that's needed is the "changing" > > attribute, but this is not the case. > > What am I missing from the config (ivy file and/or ivy settings)? > > To be more specific, the documentation says: > > > Ivy supports this kind of approach with the notion of changing revision. A > changing revision is just that: a revision for which Ivy should consider > that the artifacts may change over time. To handle this, you can either > specify a dependency as changing on the dependency tag, or use the > changingPattern and changingMatcher attributes on your resolvers to > indicate > which revision or group of revisions should be considered as changing. > > > Since this mentions an *alternative*, I used *one* of the possibilities, > namely adding the "changing" attribute (see above). > But the cache is *not* updated, as this shows: > Repository: > -rw-r--r-- 1 gilles gilles 159779 2009-05-11 15:15 > /home/dummy/ivy/repository/automatic/be.ac.ulb.iaa/gesss/jars/gesss-SNAPSHOT.jar > Cache: > -rw-r--r-- 1 gilles gilles 159782 2009-05-08 17:30 > /home/gilles/.ivy2/cache/be.ac.ulb.iaa/gesss/jars/gesss-SNAPSHOT.jar > > Can someone please confirm whether this is bug or expected behaviour? > As far as I'm guessing correctly, it should be obvious that, for a changing > revision, ivy should look up the repository to check whether a more recent > version exit there... > To make sure that an application will use the latest version stored in the > repository, there must be another way than to clean the cache each time I > run it! > > > At the end of the explanation on "changing revisions", the doc indicates: > > > So if you want to use changing revisions, use the publish task to publish > your modules, it will take care of updating the publication date, and > everything will work fine. And remember to set checkModified=true" on your > resolver too! > > > So, even as it clearly stated before that the "changing" attribute is all > that's needed, I also tried to add the "checkModified" attribute on the > resolver, but then I got the following error: > > BUILD FAILED > /home/gilles/devel/SVN/java/ecl/ant/common.xml:188: impossible to > configure > ivy:settings with given file: > /home/dummy/ivy/settings/ivysettings-local.xml: > java.text.ParseException: failed to load settings from > file:/home/dummy/ivy/settings/ivysettings-local.xml: no set method found > for > checkModified on class org.apache.ivy.plugins.resolver.FileSystemResolver > > I'm lost here. The error message is rather cryptic. > It would really be useful to have a fully functional set of ivy files in > the > section "Cache and Change Management"... > > > Regards, > Gilles > --000e0cd28df29e1aa10469b6fd91--