Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Message-ID: <427646810.1219411844516.JavaMail.jira@brutus>
Date: Fri, 22 Aug 2008 06:30:44 -0700 (PDT)
From: =?utf-8?Q?Nicolas_Lalev=C3=A9e_=28JIRA=29?= <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Resolved: (IVYDE-114) Need CleanCache task in context menu
In-Reply-To: <1730054007.1219192364209.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

Nicolas Lalev=C3=A9e resolved IVYDE-114.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0
         Assignee: Nicolas Lalev=C3=A9e

Excellent idea. I have implemented it and it works great. So I added a new =
context entry in the context menu to clean the caches. This new menu entry =
offer different kind of cache cleaning:
* clean the resolution cache
* clean every repository cache
* clean each repository cache individually
* clean every cache


> Need CleanCache task in context menu
> ------------------------------------
>
>                 Key: IVYDE-114
>                 URL: https://issues.apache.org/jira/browse/IVYDE-114
>             Project: IvyDE
>          Issue Type: Improvement
>          Components: classpath container
>    Affects Versions: 2.0.0.alpha1
>         Environment: All
>            Reporter: Kirby Files
>            Assignee: Nicolas Lalev=C3=A9e
>             Fix For: 2.0
>
>
> The classpath container supports a Resolve task on its context menu, but =
not a CleanCache. This is unfortunate, because, if the resolve fails to loc=
ate some artifacts (say, because of an intermittent DNS failure or web serv=
er outage), it records ".notfound" entries in the cache, making future Reso=
lves continue to fail.
> The only solution I've found is to create an ant build.xml with a cleanca=
che target, and run that in these situations. It would be preferable if I c=
ould clean the cache directly from the classpath container context menu. Si=
nce the ivy:cleancache task already exists, this would hopefully involve ch=
anging mostly UI code.

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