Yep, I did this. It happened when I added shadowcopyfile support. I will do
a Path.GetFullPath to resolve the problem. We should also add a test for
this. :)
----- Original Message -----
From: "Tomas Restrepo" <[EMAIL PROTECTED]>
To: "'Nant-Developers (E-mail)'" <[EMAIL PROTECTED]>
Sent: Tuesday, January 21, 2003 5:57 PM
Subject: [nant-dev] nant.location?
> Hi guys,
>
> Has anyone recently changed what value ${nant.location} gets initialized
to?
> Or has the processing of filesets changed recently?
>
> I've been having to modify some buildfiles I have because of one of these
> things, because I was doing things in a fileset like:
>
> <includes name="${nant.location}/NUnitCore.dll"/>
>
> Now, it fails because ${nant.location} apparently gets initialized with a
> terminating "\", so the resulting path ends up something like
> E:\Projects\sf\nant\build\nant-0.8.0-debug\bin\/NUnitCore.dll, which the
> fileset seems to be discarding.
>
> Any ideas?
-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
_______________________________________________
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
