Return-Path: Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org Received: (qmail 26452 invoked from network); 3 Oct 2009 16:11:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Oct 2009 16:11:47 -0000 Received: (qmail 47427 invoked by uid 500); 3 Oct 2009 16:11:47 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 47401 invoked by uid 500); 3 Oct 2009 16:11:47 -0000 Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ant.apache.org Delivered-To: mailing list notifications@ant.apache.org Received: (qmail 47392 invoked by uid 99); 3 Oct 2009 16:11:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Oct 2009 16:11:47 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Oct 2009 16:11:44 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 9075D234C004 for ; Sat, 3 Oct 2009 09:11:23 -0700 (PDT) Message-ID: <1169097962.1254586283519.JavaMail.jira@brutus> Date: Sat, 3 Oct 2009 09:11:23 -0700 (PDT) From: "jaco uys (JIRA)" To: notifications@ant.apache.org Subject: [jira] Created: (IVY-1133) ChainResolver Checkmodified override bug MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org ChainResolver Checkmodified override bug ---------------------------------------- Key: IVY-1133 URL: https://issues.apache.org/jira/browse/IVY-1133 Project: Ivy Issue Type: Bug Components: Core Affects Versions: 2.1.0-RC2 Reporter: jaco uys 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'. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.