ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Aston <>
Subject Re: <ivy:info> and <ivy:resolve> not getting the same revision
Date Tue, 31 Aug 2010 13:04:14 GMT


From:       Maarten Coene <>
Date:       08/30/2010 02:43 PM.
Subject:    Re: <ivy:info> and <ivy:resolve> not getting the same revision

Seems like a bug to me.
Could you open a JIRA ticket?
If possible, could you attach a detailed example?


----- Original Message ----
From: Timothy Aston <>
Sent: Mon, August 30, 2010 6:06:29 PM
Subject: <ivy:info> and <ivy:resolve> not getting the same revision

I'm playing around with <ivy:info>  using the organisation, module and
revision attributes, and I'm finding some inconsistencies with what version
it gets in comparison to <ivy:resolve> calls of the same module elsewhere
in my build.  I've specified a revision of "latest.integration", and my
default resolver is a chain resolver with returnFirst="true", and my local
repository is first followed by a second remote repository.

As expected, <ivy:resolve> calls throughout my build correctly take from
the local repository whenever the module in question exists there.
However, I'm finding that <ivy:info> is always pulling from the second
resolver in the chain, as if its ignoring the returnFirst="true". (the
version in the second resolve would parse out as higher than the one in the
local repository).

Is this the expected behaviour?


  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message