Title: Running NANT - Error - Path Too Long
You can always use good old subst to shorten it.
 
Something like this: subst x: "c:\reallyreally\long\but fairly\descriptive path\to the current\project"
 
This exception seems to come from the runtime classes, so there isn't much I can think of doing on the nant side to fix it.
 
On ntfs you can use join points to map one part of an ntfs drive into a alternate directory structure. Or you can use the linkd program from the reskit to create hard links in the fs too(or junction from sysinternals.com). This is all a little hokie, but you are messing with some very old limitations in windows that are going to be hard to resolve.
 
It is also possible that there is a setting somewhere in the registry to cause the system to use 8.3 path/file names in all the internal functions (like the ones that fx use). But I have no idea where this is, or if it exists. I remember something like this in the nt 3.51 days when the new shell was being introduced, but that is a pretty old memory :)
----- Original Message -----
Sent: Thursday, September 18, 2003 9:53 AM
Subject: [Nant-users] Running NANT - Error - Path Too Long

I am wondering if someone found a work-around (other than making the path name shorter) for the "path too long" error when running Nant.  Our directory structure may be two to three levels and we like to use descriptive names.

Here is the output I get that shows the error, just in case you have no idea what I am talking about  (smile):
<<output.txt>>

Thanks!

Reply via email to