Return-Path: <ecooper@ergotech.com>
Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Delivered-To: mailing list user@ant.apache.org
Received: (qmail 14320 invoked from network); 3 Apr 2003 04:41:58 -0000
Received: from mail15.speakeasy.net (HELO mail.speakeasy.net) (216.254.0.215)
  by daedalus.apache.org with SMTP; 3 Apr 2003 04:41:58 -0000
Received: (qmail 3956 invoked from network); 3 Apr 2003 04:42:20 -0000
Received: from unknown (HELO squirtle.ergotech.com) (ecooper@[68.35.1.240])
          (envelope-sender <ecooper@ergotech.com>)
          by mail15.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <user@ant.apache.org>; 3 Apr 2003 04:42:20 -0000
Message-Id: <5.2.0.9.0.20030402213701.02bcaac8@mail.speakeasy.net>
X-Sender: ecooper@mail.speakeasy.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 02 Apr 2003 21:37:53 -0700
To: "Ant Users List" <user@ant.apache.org>
From: Elizabeth Cooper <ecooper@ergotech.com>
Subject: Re: filter: Windows backslashes in a properties file 
In-Reply-To: <B15F5BF55B08D511BB1700B0D0687B46013EEC64@xifine01.xifin.co
 m>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Use ${file.separator} in your properties file instead of the backslash. It 
will be converted correctly for any OS that uses this file.

At 08:55 PM 4/2/2003, you wrote:
>My build.xml is copying a properties file and using a filterset to perform 
>substitutions during the copy.
>
>     <copy file="${src.test.dir}/templates/LorTest.properties" 
> todir="${build.test.dir}" filtering="yes">
>       <filterset>
>         <filter token="LOR_HOME" value="${basedir}"/>
>       </filterset>
>     </copy>
>
>On our Windows development machines ${basedir} is generally 
>"D:\Lor".   The resulting file is properly substituted such that any 
>occurrence of "@LOR_HOME@" is replaced with "D:\Lor".
>
>The output file is a properties file and when we load the properties at 
>runtime this string is transformed to "D:Lor" -- note the missing 
>backslash.  The resulting path is no good since it lacks that initial 
>backslash.
>
>Is there some way to handle this issue nicely?
>
>Thanks!