Return-Path: Mailing-List: contact user-help@ant.apache.org; run by ezmlm Delivered-To: mailing list user@ant.apache.org Received: (qmail 48071 invoked from network); 10 Feb 2003 16:19:41 -0000 Received: from h002.c000.snv.cp.net (HELO c000.snv.cp.net) (209.228.32.66) by daedalus.apache.org with SMTP; 10 Feb 2003 16:19:41 -0000 Received: (cpmta 10680 invoked from network); 10 Feb 2003 08:19:42 -0800 Received: from 128.143.103.6 (HELO ehatchersolutions.com) by smtp.hatcher.net (209.228.32.66) with SMTP; 10 Feb 2003 08:19:42 -0800 X-Sent: 10 Feb 2003 16:19:42 GMT Date: Mon, 10 Feb 2003 11:19:43 -0500 Subject: Re: filelist dir attribute Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) From: Erik Hatcher To: "Ant Users List" Content-Transfer-Encoding: 7bit In-Reply-To: <3E47CFF4.2090707@cyberspaceroad.com> Message-Id: <76900FF2-3D13-11D7-BE2E-000393A564E6@ehatchersolutions.com> X-Mailer: Apple Mail (2.551) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Monday, February 10, 2003, at 11:14 AM, Adam Hardy wrote: > has the same effect of putting the working > directory onto the front, and puts it onto the > front of each item. Unless there's an attribute I don't know about? I'm confused. You mean your properties like ${struts.jar} are *relative* paths? And you want to keep them that way? That is just not going to work consistently. Each JAR file property should be an absolute path to the location, not relative. This does not at all mean you code absolute paths anywhere - but instead you have a known "root" directory you can base from (perhaps ${basedir} or ".") and fix properties from that point. For example, I use something like this: And then fix paths to ${struts.jar} based on ${lib.dir}. Erik