yes -- due to cars being unpacked in the repo. I think that the assembly would build ok but when G tried to start the component something threw a FileNotFoundException due to the path length restriction in windows.
Best wishes, Paul On 3/20/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
Do you know specifically when this happens? Is this because of including it in the car, and since cars are unpacked in the repo that it makes a horribly long path? --jason On Mar 20, 2007, at 2:17 PM, Paul McMahan wrote: > It's been a while but as I recall the module name was shortened > because after being deployed into the repository the path name to some > of its resources exceeded the maximum path length on windows. > > Best wishes, > Paul > > On 3/20/07, Jason Dillon <[EMAIL PROTECTED]> wrote: >> If there is an issue, I would rather look into fixing the cause not >> pollute the name. >> >> Why exactly would the name of this artifact cause path issues for >> windows? >> >> --jason >> >> >> On Mar 20, 2007, at 5:20 AM, David Jencks wrote: >> >> > We might need to watch out for windows path length problems as a >> > result of this change -- they were the reason for the former >> > peculiar name. >> > >> > thanks >> > david jencks >> >
