Return-Path: <dcorbin@machturtle.com>
Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Delivered-To: mailing list user@ant.apache.org
Received: (qmail 87275 invoked from network); 23 Feb 2003 16:31:31 -0000
Received: from mail140.mail.bellsouth.net (HELO imf52bis.bellsouth.net)
 (205.152.58.100)
  by daedalus.apache.org with SMTP; 23 Feb 2003 16:31:31 -0000
Received: from picolo.corbin.machturtle.com ([66.156.88.125])
          by imf52bis.bellsouth.net
          (InterMail vM.5.01.04.25 201-253-122-122-125-20020815) with ESMTP
          id
 <20030223163332.PWOB12722.imf52bis.bellsouth.net@picolo.corbin.machturtle.com>
          for <user@ant.apache.org>; Sun, 23 Feb 2003 11:33:32 -0500
Received: from picolo.corbin.machturtle.com
	([192.168.26.3] helo=machturtle.com ident=dcorbin)
	by picolo.corbin.machturtle.com with esmtp (Exim 3.36 #1 (Debian))
	id 18mz2F-0001AI-00
	for <user@ant.apache.org>; Sun, 23 Feb 2003 11:31:27 -0500
Message-ID: <3E58F75E.5000508@machturtle.com>
Date: Sun, 23 Feb 2003 11:31:26 -0500
From: David Corbin <dcorbin@machturtle.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030130
X-Accept-Language: en
MIME-Version: 1.0
To: Ant Users List <user@ant.apache.org>
Subject: Re: Ant Task and paths
References: <BE8137D1-4749-11D7-896D-000393DB1D12@cryptocard.com>
In-Reply-To: <BE8137D1-4749-11D7-896D-000393DB1D12@cryptocard.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Jesse Stockall wrote:

> On Sunday, February 23, 2003, at 10:48 AM, Martin wrote:
>
>> Jesse-
>> Many of the Unix installations use Relative Path with 100% success 
>> but the
>> absolute path gets munged because
>> of the difference of the treatment of <root> between Unix vs Windoze
>> Has this been resolved?
>
>
> I'm not really sure what you are asking.
>
> If you use absolute paths they will not resolve on anything but their 
> native platform i.e.
>
> 'c:\pathname' will only work on Windows, '/pathname' will only work on 
> Unix platforms and 'volume:\pathname' will work only on NetWare
>
> If you use a relative path then Ant will resolve the path based on 
> what ${basedir} is set to. i.e.

How?  Do you mean ant will do that using the FileUtils you mentioned?  
Otherwise, I don't see how Ant will know that a given attribute/property 
is a filesystem reference.

> Path in build file = 'build/lib'
>
> On Windows if ${basedir} = 'c:\path', it will be resolved to 
> 'c:\path\build\lib'
>
> On Unix if ${basedir} = '/home/jesse', it will be resolved to 
> '/home/jesse/build/lib'
>
> I have had no problems using relative paths (cross platform) and 
> absolute paths (single platform)

When I spoke about absolute paths, what I meant was this:  as the writer 
of the build.xml, I can convert all relative paths by an explicit 
reference to ${basedir}.  What I was unsure of, was if requireing this 
was standard behavior for tasks, or not.   Apparently not.

>
> Jesse Stockall - jesse@cryptocard.com
> CRYPTOCard Corp.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
>