I've tried deleting all references to the module I'm trying to resolve but
it continues to look for the old value. :-(
The ivy.xml must be cached somewhere else I don't know about.
On Wed, Jun 18, 2008 at 4:32 PM, Jim White <[EMAIL PROTECTED]> wrote:
> I don't know any of the details involved with what's happened with what you
> describe, but it sounds to me like clearing the Ivy cache may fix it.
>
> It is located at "${user.home}/.ivy2" and if you've got a bunch of stuff
> you don't want to lose, you can go in and just delete the subdirectory that
> you suspect is incorrect.
>
> A "flush cache" option that caused any entries involved in resolution to be
> invalidated would be nice. That way this sort of problem could be
> (possibly) fixed without wiping out the (possibly large) entire cache.
>
> Jim
>
>
> Dave wrote:
>
> Hey all,
>> I had an Ivy file with a bad dependency. The organisation attribute was
>> set
>> to an incorrect value. I've now changed that value, but Ivy keeps trying
>> to
>> resolve with the old value.
>> In my Ivy settings file I'm using a chain resolver which contains the
>> following
>> Local -> Shared -> Maven2
>> repositories.
>>
>> All have the checkmodified attribute set to true, including the chain
>> resolver itself.
>> What am I doing wrong. How can I force Ivy to see the new value and
>> resolve
>> it?
>>
>> /Dave
>>
>>
>
--
There are 10 types of people in the world.
Those who understand binary and those who do not.
