Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (athena.apache.org: domain of james@banshee.com designates
 209.85.213.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CADWsF0Nqf6+k998sN5yZcYakJ3QxnCzSPJJCghSk6USjMR8gRw@mail.gmail.com>
References: 
 <CADWsF0Nqf6+k998sN5yZcYakJ3QxnCzSPJJCghSk6USjMR8gRw@mail.gmail.com>
From: James Moore <james@restphone.com>
Date: Tue, 27 Mar 2012 11:27:36 -0700
Message-ID: 
 <CAPBr=W93K9WZJXiqKjn-1+s2NQ=p821JL84dSbZbpJox9E1F_Q@mail.gmail.com>
Subject: Re: windows vs linux paths in properties
To: ivy-user@ant.apache.org
Content-Type: multipart/alternative; boundary=0016e6d27c859fa48404bc3da7b6

--0016e6d27c859fa48404bc3da7b6
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Mar 27, 2012 at 7:27 AM, Jasper Floor <jasper.floor@m4n.nl> wrote:

> This fails terribly in windows because of the /
> The reason, obviously is that the / should be a \ in windows.\
>

That shouldn't be the problem; both \ and / are file separators in Windows
and always have been.  There are some Windows tools that use / as something
other than a file separator (like cmd), but that's a specific issue for
that specific tool.

-- 
James Moore
james@restphone.com
http://blog.restphone.com/
http://www.linkedin.com/in/jamesmmooreiv

--0016e6d27c859fa48404bc3da7b6--