Return-Path: Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org Received: (qmail 40768 invoked from network); 23 Feb 2007 12:43:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Feb 2007 12:43:09 -0000 Received: (qmail 1485 invoked by uid 500); 23 Feb 2007 12:43:17 -0000 Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org Received: (qmail 1465 invoked by uid 500); 23 Feb 2007 12:43:17 -0000 Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@incubator.apache.org Delivered-To: mailing list ivy-user@incubator.apache.org Received: (qmail 1449 invoked by uid 99); 23 Feb 2007 12:43:17 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Feb 2007 04:43:17 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [194.199.18.100] (HELO mx-serv.inrialpes.fr) (194.199.18.100) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Feb 2007 04:43:05 -0800 Received: from vilnius.inrialpes.fr (vilnius.inrialpes.fr [194.199.18.81]) by mx-serv.inrialpes.fr (8.13.6/8.13.0) with ESMTP id l1NCgcNU008454 for ; Fri, 23 Feb 2007 13:42:38 +0100 (MET) Received: from [194.199.22.142] (listeria.inrialpes.fr [194.199.22.142]) by vilnius.inrialpes.fr (8.13.6/8.11.3/ImagV2) with ESMTP id l1NCgbnH029060 for ; Fri, 23 Feb 2007 13:42:37 +0100 (MET) Message-ID: <45DEE151.2070505@genostar.com> Date: Fri, 23 Feb 2007 13:42:57 +0100 From: Gilles Faucherand User-Agent: Thunderbird 1.5.0.9 (X11/20061206) MIME-Version: 1.0 To: ivy-user@incubator.apache.org Subject: Re: eviction and conflict manager References: <45DECA65.3050201@genostar.com> <635a05060702230324g25f2fd34m912b799b5d8c0c6d@mail.gmail.com> In-Reply-To: <635a05060702230324g25f2fd34m912b799b5d8c0c6d@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (mx-serv.inrialpes.fr [194.199.18.100]); Fri, 23 Feb 2007 13:42:38 +0100 (MET) X-mx-serv-inrialpes-fr-MailScanner-Information: Please contact postmaster@inrialpes.fr for more information X-mx-serv-inrialpes-fr-MailScanner: Found to be clean X-mx-serv-inrialpes-fr-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=0, requis 5) X-mx-serv-inrialpes-fr-MailScanner-From: gilles.faucherand@genostar.com X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No Xavier Hanin wrote: > On 2/23/07, Gilles Faucherand wrote: >> >> Hi, >> >> I have some problems with eviction strategy. I set a >> defaultConflictManager="latest-time" >> in my ivyconf meaning for me if a conflict appears to retrieve all the >> time the last in time published. >> >> Say for instance that I have 3 modules A, B and C. >> 1) I publish C-1.0.0 and later C-1.0.1. >> 2) B needs C-1.0.0, I retrieve (ok) and I publish B-1.0.0 >> 3) A needs B-1.0.0 and C-1.0.1 (order is important: B before C in ivy >> file ...) >> >> When I retrieve I get C-1.0.0 ??? >> [resolve] :: evicted modules: >> [resolve] [ MyCompany | C | 1.0.1 ] by [[ MyCompany | C | 1.0.0 ]] >> in [all] >> [resolve] in [ MyCompany | A | 1.0.0 ] with latest-time >> >> If I change the order in the ivy file i.e. C before B, I get what I want >> C-1.0.1 ... >> [resolve] :: evicted modules: >> [resolve] [ MyCompany | C | 1.0.0 ] by [[ MyCompany | C | 1.0.1 ]] >> in [all] >> [resolve] in [ MyCompany | B | 1.0.0 ] with latest-time >> >> Is it normal ? > > > No, this is not normal. The only reason why this should happen is if > the two > revision are considered equal according to the latest revision strategy > used, in your case latest-time. So this should only happen if the two > have > the same time of publication. Note that Ivy uses the publication time > in the > Ivy file during conflict resolution, so make sure you have set the > publication attribute in your ivy files in your repository. You mean in the ivy file of the module C No, or I should change this date each time I publish and I've got a nightly builder ... After publication in the repository the ivy file created was myrepos/MyCompany/C/ivy-1.0.0.xml (following my ivy artifact pattern) ... A publication date is set ... I thought this date was used ? > If you still > have the problem, you can open a JIRA issue describing your problem > and your > environment. > > Xavier > > > > Thanks in advance, >> Gilles >> >> >