Use "location" instead of "value" in your property task. It will
normalize the path and also document that you are dealing with files
instead of arbitrary strings.
Here's an example:
buildDir-value = ${buildDir-value}
buildDir-location = ${buildDir-location}
InstallShieldComp
Try the task. Then you don't have to remember to put the right separator
in when defining properties.
/mike
> -Original Message-
> From: Stephenson, Martin [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 03, 2002 6:27 AM
> To: '[EMAIL PROTECTED]'
> Subject: Path question
>
>
>
- Original Message -
From: "Stephenson, Martin" <[EMAIL PROTECTED]>
> ...
> F:\Development/Builds/1.0.0.0/ISComponents
>
> But the program I'm calling doesn't like the forward-slash - it want's
> Backslashes, ie.:
>
> F:\Development\Builds\1.0.0.0\ISComponents
>
> Is there some way I can
Martin,
Typically you want to assign properties which specify paths with the
location attribute:
This will assign the property the appropriate canonical filename for host
os.
I am working on a filter that will adjust paths specified in a property file
in the same way and hope to make it avail
try using the "location" attribute of . i.e.
--
knut
> -Original Message-
> From: Stephenson, Martin [mailto:[EMAIL PROTECTED]]
> Sent: Donnerstag, 3. Oktober 2002 15:27
> To: '[EMAIL PROTECTED]'
> Subject: Path question
>
>
> Hi all
>
> I have a property called "b
On Fri, 13 Jul 2001, Fernando Padilla <[EMAIL PROTECTED]>
wrote:
> I have just been attempting to use a path element from within a
> task.
More than just nitpicking: You mean target here 8-)
> Ant 1.3 will not allow me to do this.
Right, this has been identified as a problem and will be fixed
