Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Message-ID: <4656545.194321288704168180.JavaMail.jira@thor>
Date: Tue, 2 Nov 2010 09:22:48 -0400 (EDT)
From: =?utf-8?Q?Nicolas_Lalev=C3=A9e_=28JIRA=29?= <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Resolved: (IVY-1243) UseCacheOnly is influenced by the TTL
 on cached metadata
In-Reply-To: <31298230.194021288703664951.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/IVY-1243?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicolas Lalev=C3=A9e resolved IVY-1243.
----------------------------------

       Resolution: Fixed
    Fix Version/s: trunk

> UseCacheOnly is influenced by the TTL on cached metadata
> --------------------------------------------------------
>
>                 Key: IVY-1243
>                 URL: https://issues.apache.org/jira/browse/IVY-1243
>             Project: Ivy
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>            Reporter: Nicolas Lalev=C3=A9e
>            Assignee: Nicolas Lalev=C3=A9e
>             Fix For: trunk
>
>
> When using useCacheOnly=3Dtrue, I expect Ivy to only use the cache, so ma=
ke Ivy trust the cached data.
> But it takes into account the time to live on cached metadata, and conseq=
uently reject those metadata, resulting on an unexpected failing resolve.
> I would expect Ivy to ignore the TTL configuration in the useCacheOnly mo=
de.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.