Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 61720 invoked from network); 5 Mar 2008 12:17:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Mar 2008 12:17:50 -0000 Received: (qmail 67828 invoked by uid 500); 5 Mar 2008 12:17:46 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 67642 invoked by uid 500); 5 Mar 2008 12:17:45 -0000 Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@ant.apache.org Delivered-To: mailing list ivy-user@ant.apache.org Received: (qmail 67633 invoked by uid 99); 5 Mar 2008 12:17:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Mar 2008 04:17:45 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [212.227.126.188] (HELO moutng.kundenserver.de) (212.227.126.188) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Mar 2008 12:16:58 +0000 Received: from [192.168.2.100] (p4FE263A9.dip.t-dialin.net [79.226.99.169]) by mrelayeu.kundenserver.de (node=mrelayeu0) with ESMTP (Nemesis) id 0MKwh2-1JWsYg48Qa-00064C; Wed, 05 Mar 2008 13:17:19 +0100 Mime-Version: 1.0 (Apple Message framework v753) Content-Transfer-Encoding: 7bit Message-Id: <26E3BC92-B345-40A2-B958-3A5514002539@dockter.biz> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: ivy-user@ant.apache.org From: Hans Dockter Subject: Error message when using different settings Date: Wed, 5 Mar 2008 13:17:17 +0100 X-Mailer: Apple Mail (2.753) X-Provags-ID: V01U2FsdGVkX1+CxeXUi7OYIXodFVcI5skbmnOT9AfYANsB5hP wNNAqtSfWBhzYmCARq5tcV85qN+nH8CZghgj6W+QUnVExXTgTA W4Vg+KJxQP3RerHG8ldog== X-Virus-Checked: Checked by ClamAV on apache.org In my environment I use multiple settings to work with Ivy. One setting is the ivysettings.xml for building my build tool. The other setting is when I use my build tool which defines its own resolvers. If for example my build tool has been executed and has used Ivy to resolve a dependency that is also used by the build of my build tool, I get the following messages when building my build tool (chain is the name of a resolver defined by my build tool). [ivy:cachepath] == resolving dependencies org.gradle#gradle;working@localhost->commons-lang#commons-lang;2.3 [compile->default] [ivy:cachepath] loadData of commons-lang#commons-lang;2.3 of rootConf=compile [ivy:cachepath] using default to resolve commons-lang#commons- lang;2.3 [ivy:cachepath] default: Checking cache for: dependency: commons- lang#commons-lang;2.3 {compile=[default]} Resource org/apache/ivy/plugins/parser/xml/ivy.xsd loaded from ant loader [ivy:cachepath] pre 1.3 ivy file: using exactOrRegexp as default matcher [ivy:cachepath] ERROR: unknown resolver chain [ivy:cachepath] resolver not found: chain => trying to use the one configured for commons-lang#commons-lang;2.3 [ivy:cachepath] configured resolver found for commons- lang#commons-lang;2.3: default: saving this data [ivy:cachepath] ERROR: unknown resolver chain [ivy:cachepath] found ivy file in cache for commons- lang#commons-lang;2.3 (resolved by default): /Users/hans/.ivy2/cache/ commons-lang/commons-lang/ivy-2.3.xml [ivy:cachepath] default: module revision found in cache: commons- lang#commons-lang;2.3 [ivy:cachepath] found commons-lang#commons-lang;2.3 in default Everything works but for me ERROR messages in the build log are very irritating if everything is OK. This problem has also been there with Ivy beta1 and is still there with Ivy beta2. - Hans