Return-Path: 
 <ivy-user-return-6979-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-ivy-user-archive@www.apache.org
Received: (qmail 65597 invoked from network); 14 Jul 2010 06:40:49 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 14 Jul 2010 06:40:49 -0000
Received: (qmail 29645 invoked by uid 500); 14 Jul 2010 06:40:49 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 29278 invoked by uid 500); 14 Jul 2010 06:40:46 -0000
Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ivy-user-help@ant.apache.org>
List-Unsubscribe: <mailto:ivy-user-unsubscribe@ant.apache.org>
List-Post: <mailto:ivy-user@ant.apache.org>
List-Id: <ivy-user.ant.apache.org>
Reply-To: ivy-user@ant.apache.org
Delivered-To: mailing list ivy-user@ant.apache.org
Received: (qmail 29270 invoked by uid 99); 14 Jul 2010 06:40:45 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Jul 2010 06:40:45 +0000
X-ASF-Spam-Status: No, hits=2.9 required=10.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Received: from [212.227.17.10] (HELO moutng.kundenserver.de) (212.227.17.10)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Jul 2010 06:40:38 +0000
Received: from mail-ww0-f47.google.com (mail-ww0-f47.google.com
 [74.125.82.47])
	by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis)
	id 0M5Ijf-1PILPg3EeF-00zH0Y; Wed, 14 Jul 2010 08:39:47 +0200
Received: by wwi14 with SMTP id 14so1858580wwi.16
        for <ivy-user@ant.apache.org>; Tue, 13 Jul 2010 23:39:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.165.132 with SMTP id e4mr11322178wel.83.1279089585974;
	Tue, 13 Jul 2010 23:39:45 -0700 (PDT)
Received: by 10.216.138.94 with HTTP; Tue, 13 Jul 2010 23:39:45 -0700 (PDT)
In-Reply-To: <812857.80297.qm@web30802.mail.mud.yahoo.com>
References: <AANLkTimyKB8JMWO9DvXBPYMwSB2r5Kz_6ZANcvrX-My3@mail.gmail.com>
	<812857.80297.qm@web30802.mail.mud.yahoo.com>
Date: Wed, 14 Jul 2010 08:39:45 +0200
Message-ID: <AANLkTimFVNmyhsyANd3RAO-P-6DX-psDtcjRSC6v0t-H@mail.gmail.com>
Subject: Re: Update policy for Maven snapshots
From: Hans Dockter <mail@dockter.biz>
To: ivy-user@ant.apache.org
Content-Type: multipart/alternative; boundary=001636416a99686d94048b5340af
X-Provags-ID: V02:K0:Zb3o0uNsZn7tuHZ/O4MudKUUOvfqd8atwMElidl/98i
 m8UAvgygqthJni9lBvC4ce+O8FVLxenq9ja6v7eutgOZm8hcmX
 LTVymD965pHmjr1YEspCkhKp/mS7D1eyOwWhWNMZE+r2+VGCMf
 GWaA0lhlZGMXd2d5eOY5U7SF7uuu/mOTM6MN23SDbFPKEdmNk7
 4x/Kd0CsgLvCi6UO7Pt3ppiyvzM6Hkhf2PDFI8bk40=
X-Virus-Checked: Checked by ClamAV on apache.org

--001636416a99686d94048b5340af
Content-Type: text/plain; charset=ISO-8859-1

Hi Marteen,

On Wed, Jul 14, 2010 at 12:23 AM, Maarten Coene <maarten_coene@yahoo.com>wrote:

> Did you look at the 'defaultTTL' attribute on the <cache> element in your
> settings.xml ?
>
> http://ant.apache.org/ivy/history/latest-milestone/settings/caches/cache.html


thanks a lot for pointing this out. This works fine for me with dynamic Ivy
revisions (e.g. 4.+). But for Maven snapshots it seems not to work.

I think this might be related to the IBibilioResolver using a changing
pattern. In the debug output I get the following for Maven snapshots:

*don't use cache for org.grails#grails-resources;1.1.1-SNAPSHOT:
changing=true*

**So the TTL do not seem to hook in for snapshots as the cache seems to be
circumvented in any case.

The only solution I can think of is either modifying IBiblio or adding a
custom resolver that points to the ivy cache which only resolves SNAPSHOT
according to a timing pattern. Anything else you can think of?

Thanks

- Hans

--
Hans Dockter
Founder, Gradle
http://www.gradle.org, http://twitter.com/gradleorg
CEO, Gradle Inc. - Gradle Training, Support, Consulting
http://www.gradle.biz


>
>
> Maarten
>
>
>
>
> ----- Original Message ----
> From: Hans Dockter <hans@gradle.biz>
> To: ivy-user@ant.apache.org
> Sent: Tue, July 13, 2010 5:27:24 PM
> Subject: Update policy for Maven snapshots
>
> Hi,
>
> is there any standard way in Ivy to express the Maven feature of a
> snapshot-policy? The latter allows you to define the frequency for an up to
> date check:
>
> always - always check when Maven is started for newer versions of snapshots
> never - never check for newer remote versions. Once off manual updates can
> be performed.
> daily (default) - check on the first run of the day (local time)
> interval:XXX - check every XXX minutes
>
> I think such a policy makes sense in particular if your repo is accessed
> via
> the internet vs. an intranet company repo. Otherwise using snapshots
> carries
> a high performance penalty.
>
> - Hans
>
> --
> Hans Dockter
> Founder, Gradle
> http://www.gradle.org, http://twitter.com/gradleorg
> CEO, Gradle Inc. - Gradle Training, Support, Consulting
> http://www.gradle.biz
>
>
>
>
>

--001636416a99686d94048b5340af--