Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (nike.apache.org: domain of jaco.uys@gmail.com designates
 209.85.222.181 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:reply-to:date:message-id:subject:from:to:content-type;
        b=xW9PzHVjbqXoyiDPi3Oe5THNh4xJcaMAm0BMQ7slzWqzQauQA0FFGocAaJXZWrt+K5
         nuj/CwdA7iCq/I+MkbOReQBsESkRQmEbTqRNKbEhC1caAqU1uowB76Hda41simP5uc6A
         Q3EAwYR2HddvaXTbZe5bGuu6wlmVb9OymDD+o=
MIME-Version: 1.0
Reply-To: jaco.uys@gmail.com
Date: Fri, 2 Oct 2009 13:27:56 +0200
Message-ID: <fcf6f6b50910020427y25a5ec0ftaa567b4462c5ab28@mail.gmail.com>
Subject: possible bug in ChainResolver
From: Jaco Uys <jaco.uys@gmail.com>
To: ivy-user@ant.apache.org
Content-Type: multipart/mixed; boundary=000e0cd312d63e26510474f20e71

--000e0cd312d63e26510474f20e71
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I have found an issue some time ago with resolving dependencies via a
chain resolver.
I can not remember the exact scenario, but had to do with resolving A
-> B -> C where A and C comes from a local repo and B from a 'shared'
repo.

The issue seems to be with ChainResolver that overrides 'public void
setCheckmodified(boolean check)'. The 'checkModified' value is not
propagated through to the base class 'AbstractResolver'. This results
in the 'AbstractResolver.getCacheOptions(ResolveData data)' behaving
incorrectly when creating the 'CacheMetadataOptions'.

The fix I made was to change the 'ChainResolver.setCheckmodified' to:

public void setCheckmodified(boolean check) {
        checkmodified = Boolean.valueOf(check);
        super.setCheckmodified(check);
}

I've attached an svn patch for it.

Regards Jaco

--000e0cd312d63e26510474f20e71--