Return-Path: Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org Received: (qmail 57124 invoked from network); 15 Nov 2006 15:11:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Nov 2006 15:11:36 -0000 Received: (qmail 46751 invoked by uid 500); 15 Nov 2006 15:11:39 -0000 Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org Received: (qmail 46632 invoked by uid 500); 15 Nov 2006 15:11:39 -0000 Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@incubator.apache.org Delivered-To: mailing list ivy-user@incubator.apache.org Received: (qmail 46571 invoked by uid 99); 15 Nov 2006 15:11:38 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Nov 2006 07:11:38 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [192.6.10.2] (HELO colossus.hpl.hp.com) (192.6.10.2) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Nov 2006 07:11:23 -0800 Received: from localhost (localhost.localdomain [127.0.0.1]) by colossus.hpl.hp.com (Postfix) with ESMTP id 18FA46BA06 for ; Wed, 15 Nov 2006 15:11:02 +0000 (GMT) X-Virus-Scanned: amavisd-new at hplb.hpl.hp.com Received: from colossus.hpl.hp.com ([127.0.0.1]) by localhost (colossus.hpl.hp.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id oSywMvNew-n4 for ; Wed, 15 Nov 2006 15:11:01 +0000 (GMT) Received: from ha-node-br1.hpl.hp.com (ha-node-br1.hpl.hp.com [16.25.144.56]) by colossus.hpl.hp.com (Postfix) with ESMTP id E3D3F6B9DF for ; Wed, 15 Nov 2006 15:10:59 +0000 (GMT) Received: from [16.25.171.182] (chamonix.hpl.hp.com [16.25.171.182]) by ha-node-br1.hpl.hp.com (8.13.4/8.13.4) with ESMTP id kAFFAlIv015595 for ; Wed, 15 Nov 2006 15:10:47 GMT Message-ID: <455B2D0F.3090505@apache.org> Date: Wed, 15 Nov 2006 15:06:55 +0000 From: Steve Loughran User-Agent: Thunderbird 1.5.0.8 (X11/20061025) MIME-Version: 1.0 To: ivy-user@incubator.apache.org Subject: resolution of relative paths in Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-HPL-MailScanner-Information: Please contact the ISP for more information X-HPL-MailScanner: Found to be clean X-HPL-MailScanner-From: stevel@apache.org X-Virus-Checked: Checked by ClamAV on apache.org Sometimes when people ask me what I do for a living, I say "I break things". Its why I'm so good at what I do: I'm inherently clumsy. Today I have a project with buildlist this includes files which import configurations This is failing, because the relative path is being resolved in the base directory, not relative to the ivy file itself. /home/slo/Projects/SmartFrog/Forge/core/build.xml:358: impossible to parse ivy file for /home/slo/Projects/SmartFrog/Forge/core/testharness/build.xml: ivyfile=/home/slo/Projects/SmartFrog/Forge/core/testharness/ivy.xml exception=java.text.ParseException: problem occured while parsing ivy file. message: /home/slo/Projects/SmartFrog/Forge/core/../antbuild/ivy/configurations.xml (No such file or directory) in file:/home/slo/Projects/SmartFrog/Forge/core/testharness/ivy.xml Defect? -Steve