Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (athena.apache.org: domain of cblistserv@gmail.com
 designates 209.85.211.204 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject
         :content-type:content-transfer-encoding;
        b=X58gC/Q/nR1/Nw8XvTSKPFEl2ySjqwNbzXw3eWs5DDFCiCMgxkPIiE0sdR/AQSi4i0
         JThZobLtogEyf3jU+RwblDmgQox59Fuji1ZacwuYlC/T5OWVhd68b98f+LHJSQ3S6fF5
         OkL9aWEXqeB+uEmF0PSUPjehRmsQfIw5gFjNc=
Message-ID: <4B55EFBC.3020908@gmail.com>
Date: Tue, 19 Jan 2010 12:45:32 -0500
From: Carlton Brown <cblistserv@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: ivy-user@ant.apache.org
Subject: TTL not applied when using resolver attributes changingRevision or
 checkModified
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I have observed that TTL rules are not applied when a URL resolver uses 
the changingPattern or checkmodified attribute.

For example, a definition like:
<url name="thirdparty" changingPattern=".*SNAPSHOT" 
latest="latest-revision" checkmodified="true">

does not respect the TTL, but if you remove changingPattern and 
checkmodified, then it complies with the TTL.

I believe it is preferable that the TTL should be effective even if 
these properties are specified on the resolver.   If my cache is fully 
populated, then an infinite TTL should permit me to work comletely offline.

Does anyone agree/disagree that a JIRA should be opened for this?

Thanks,
Carlton