ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jasper Floor <>
Subject Re: windows vs linux paths in properties
Date Wed, 28 Mar 2012 08:43:52 GMT
On Tue, Mar 27, 2012 at 8:52 PM, Matt Hurne <> wrote:
> On Tue, Mar 27, 2012 at 2:27 PM, James Moore <> wrote:
>> On Tue, Mar 27, 2012 at 7:27 AM, Jasper Floor <> 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.
> Jasper, can you be more specific about what behavior you see when
> using forward slashes (/)?  Like the others, I double-checked and can
> confirm that we are using forward slashes in <property> elements in
> our ivysettings.xml on Windows without issue.  Notice the difference
> though: you said you are having issues with the <properties> element,
> not the <property> element that we are using them in without issue.
> We are not currently using the <properties> element, but maybe I'll
> try it when I get a chance.

One of the properties files being loaded above contains the
credentials for our Nexus. No anonymous access allowed (sysadmin
decision). Using the  ${file.separator} at least made the path look
normal. Unfortunately Nexus still only seems to allow you in if you
have every single right. That is another problem however. So I thought
the credentials weren't being loaded, and I think I saw evidence of
that in the output (ant -d -v). I'll test it again just to confirm
this, but it might take a while. I don't work with windows here so I
have to corner someone who does.


View raw message