Thanks for the help. Do you have any suggestions about how I could use
pathconvert in the following context without bloating out my build file?
<copy file="${template.file}"
tofile="${destination.file}"
overwrite="true">
<filterset>
<filter token="PATH_1" value="${path.1}"/>
<filter token="PATH_2" value="${path.2}"/>
<filter token="PATH_3" value="${path.3}"/>
</filterset>
</copy>
> -----Original Message-----
> From: Steve Loughran [mailto:[EMAIL PROTECTED]
> Sent: Tuesday 09 January 2007 16:39
> To: Ant Users List
> Subject: Re: Convert property that is a path to a resource
>
> Daffin, Miles (IT) wrote:
> > Hi All,
> >
> > I have a build with a number of properties that are paths to
> > directories. I write these into a template script file using a
> > filterset during a copy. The problem is that the properties
> have mixed
> > windows and unix path separators, so when they are written into the
> > scripts they are invalid. This does not matter when the
> properties are
> > used in operations by ant (e.g. mkdir or copy) because ant/java
> > normalises the property for the platform (i.e. changes all
> separators
> > to '/' on unix or '\' on windows). Is there a way of making
> sure that
> > the same thing happens when I use these properties to
> replace tokens
> > in the filterset? Can I convert them somehow?
> >
>
> <pathconvert> does all this fixup
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED] For
> additional commands, e-mail: [EMAIL PROTECTED]
>
>
--------------------------------------------------------
NOTICE: If received in error, please destroy and notify sender. Sender does not
intend to waive confidentiality or privilege. Use of this email is prohibited
when received in error.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
