I believe you're confusing the purposes of repositories and caches.
Please review the cache concept -
http://ant.apache.org/ivy/history/latest-milestone/concept.html#cache
You should _not_ be using cache as a repository; don't point both a
resolver and a cache to the same directory structure. T
Hi Jonathan,
I've messed with this challenge with varying levels of success.
The primary issue is if you're changing a few modules (say A, B, and C) and
those modules have interdependencies (say C depends on A). If you go
parallel, C is likely to resolve the old version of A.
Not saying it can'
I think you can use Override to force the transitive dependency to the
higher version.
http://ant.apache.org/ivy/history/2.0.0/ivyfile/override.html
~Sent from my mobile device. Please pardon any oddities :-)
On Jul 27, 2011, at 4:18 AM, David Sills wrote:
> All:
>
> I have a project that has
We actually have this working. Had the same issue, but I don't recall
exactly what the cause was. (it's been a while)
I'll dig into my current setup and see how it differs, perhaps we can sort
it out.
I'm running OSX, Galileo SR2, but with Ivy 2.2.x-local-20091117220235 and
IvyDE 2.1.0.200911161
versions, haven't looked at them
> recently.
>
> ---
> Shawn Castrianni
>
>
> -Original Message-
> From: Tim Brown [mailto:tpbr...@gmail.com]
> Sent: Thursday, January 13, 2011 9:21 AM
> To: ivy-u...@ant.apache.org
> Subject: Re: Publishing C-module ar
