From ivy-commits-return-81-apmail-incubator-ivy-commits-archive=incubator.apache.org@incubator.apache.org Fri Dec 22 07:39:42 2006 Return-Path: Delivered-To: apmail-incubator-ivy-commits-archive@locus.apache.org Received: (qmail 67627 invoked from network); 22 Dec 2006 07:39:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Dec 2006 07:39:41 -0000 Received: (qmail 46984 invoked by uid 500); 22 Dec 2006 07:39:49 -0000 Delivered-To: apmail-incubator-ivy-commits-archive@incubator.apache.org Received: (qmail 46955 invoked by uid 500); 22 Dec 2006 07:39:48 -0000 Mailing-List: contact ivy-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-dev@incubator.apache.org Delivered-To: mailing list ivy-commits@incubator.apache.org Received: (qmail 46946 invoked by uid 99); 22 Dec 2006 07:39:48 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Dec 2006 23:39:48 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Dec 2006 23:39:00 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id BFE43714295 for ; Thu, 21 Dec 2006 23:38:21 -0800 (PST) Message-ID: <16554169.1166773101767.JavaMail.jira@brutus> Date: Thu, 21 Dec 2006 23:38:21 -0800 (PST) From: "Gilles Scokart (JIRA)" To: ivy-commits@incubator.apache.org Subject: [jira] Commented: (IVY-358) erase/unpublish from a file based resolver In-Reply-To: <27931534.1166727020970.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ http://issues.apache.org/jira/browse/IVY-358?page=comments#action_12460398 ] Gilles Scokart commented on IVY-358: ------------------------------------ Wouldn't it be better to have an unpublish task ? This kind of task is very dangerous with a share repository (where you don't know if an revision is still usefull or not)), but would indeed be usefull for private and snapshot repository. See also IVY-321. > erase/unpublish from a file based resolver > ------------------------------------------ > > Key: IVY-358 > URL: http://issues.apache.org/jira/browse/IVY-358 > Project: Ivy > Issue Type: Improvement > Components: Core > Affects Versions: 1.4, 1.4.1 > Environment: Linux / Any > Reporter: Eric Crahen > Priority: Minor > > I have a use case in which I set up a resolver chain that goes like this : > > > In order to make local changes to packages that I would otherwise > resolve with the url resolver, I check out the source, and publish > the override to my filebased resolver. This enables me to "override" > locally certain packages for development. > Now at some point those local changes are no longer needed, either > I decide I don't need them, someone else has merged the changes > up into the release that can be obtained from the url-resolver, whatever. > At this point, I no longer need the local "override" in my filebased-resolver. > What I would like to do is unpublish the artifact there. I don't want to go > in by hand, and remove things from my cache or delete things manually > from the file based resolver. > One solution would be something like in order to "unpublish" is would > publish to a different resolver > > This resolver might be just like the filebased-resolve, except that it does the > opposite. Instead of copying a local artifact to the resolver location, it "unpublishes" > by locating the artifact in the filebased resolver and removes it. The verb publish > means to delete the artifact with this resolver. > What this lets me do is manage my overrides (which is really just artifacts) > using ivy and not manually file hunting. > I can write ant tasks that would just publish to the erasing/unpublish resolver > in order to remove a local override. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira