Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of xavier.hanin@gmail.com
 designates 64.233.184.228 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=ppK4JFGd9RyfzN79MFiwb/e7hGRQwMYsKwUNI2RMjWYkMCDXFU3ZqpAxYhYbOCPvCi5NtKdyGEiKKvvufGF5mXkwsCIPdHQVKeM2Cavkh5qpe5TV0WhOZeXNPuMjRUdvVa0MHhszZiKK/9lt1jTjzNWA6si23RRhgIyAhwOfe4c=
Message-ID: <635a05060702230519n76aa92b9ve747f407d4225ce0@mail.gmail.com>
Date: Fri, 23 Feb 2007 14:19:26 +0100
From: "Xavier Hanin" <xavier.hanin@gmail.com>
To: ivy-user@incubator.apache.org
Subject: Re: eviction and conflict manager
In-Reply-To: <45DEE151.2070505@genostar.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_46718_15906444.1172236766073"
References: <45DECA65.3050201@genostar.com>
	 <635a05060702230324g25f2fd34m912b799b5d8c0c6d@mail.gmail.com>
	 <45DEE151.2070505@genostar.com>

------=_Part_46718_15906444.1172236766073
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 2/23/07, Gilles Faucherand <gilles.faucherand@genostar.com> wrote:
>
> Xavier Hanin wrote:
> > On 2/23/07, Gilles Faucherand <gilles.faucherand@genostar.com> 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  <info organisation="MyCompany"
> module="C" ... publication="xxxxx"  >
> 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)
>
> <?xml version="1.0" encoding="UTF-8"?>
> <ivy-module version="1.0">
>   <info organisation="MyCompany" module="C" revision="1.0.0"
> status="integration" publication="20070223132315"/>
> ...
> </ivy-module>
>
> A publication date is set ... I thought this date was used ?


Yes, this the one which should be used: the ivy file for C 1.0.0 and the one
for C 1.0.1 in your repository. Compare the two publication dates and make
sure they are different. But I realize that during conflict resolution, the
ivy files are not downloaded, so it seems to be a bug in Ivy to try to rely
on this publication date in the ivy file. It should better rely on the last
modified timestamp of the file. Could you please add an issue in JIRA?

- Xavier


> If you still
> > have the problem, you can open a JIRA issue describing your problem
> > and your
> > environment.
> >
> > Xavier
> >
> >
> >
> > Thanks in advance,
> >> Gilles
> >>
> >>
> >
>
>

------=_Part_46718_15906444.1172236766073--