I can't reproduce it... It was most probably for an other reasons. If it happen again, I will reinvestigate.
Anyway, in the meantime I have written a unit test for that, so I will enter an jira issue anyway to post the patch. Thanks, Gilles > -----Original Message----- > From: Xavier Hanin [mailto:[EMAIL PROTECTED] > Sent: Tuesday, January 16, 2007 7:01 PM > To: [email protected] > Subject: Re: Are released version considered as integration version ? > > On 1/16/07, Gilles Scokart <[EMAIL PROTECTED]> wrote: > > > > > > > > I just tried to run with the latest version, and got what I > think is a > > regression. > > > > It might be something else, but I have the impression that > previously > > (I think in 1.4.1), when I asked for latest.integration > dependency, I > > could obtained the release version if they were the most recent. > > > Yes, it was suppose to do so. > > Now, with the most recent (unreleased) version, it seems that > ivy verify the > > status of the module. So, when I only have released version, my > > resolve fails. > > > This is strange and clearly a bug. Add an an issue with a > critical severity, this absolutely needs to be fixed. > > Xavier > > Is it possible or did I have to search for an other > explanation? And if it > > the right explanation, was it a bug or a feature? > > > > > > SCOKART Gilles > > > > > > >
