Paths too long when installing STS 2.3.0

Hi, when I use WinRar to unzip springsource-tool-suite-2.3.0.RELEASE-e3.5.1-win32.zip I get the following message even if I unzip to c: !

! ...\springsource-tool-suite-2.3.0.RELEASE-e3.5.1-win32.zip: Cannot create springsource\sts-2.3.0.RELEASE\plugins\org.eclipse.contribution.xre f.source_2.0.1.e35x-20091001-1600\src\org.eclipse.contribution.xref.ui_2.0.1.e3 5x-20091001-1600\src\org\eclipse\contribution\xref\internal\ui \actions\XReferenceCustomFilterActionInplace.java
Total path and file name length must not exceed 260 characters
! The handle is invalid.

Hi SpringSource... any response to this? My client is not very impressed....

Hi,

Sorry to see you are having trouble. We are working to reduce the path lengths by repackaging that offending component of the install.

In the interim you may have better luck using another unpacking tool, I've just successfully unpacked it using 7-zip (free) and using 'jar -xvf' (and I confirmed winrar didn't work).

Failing that you could try the .exe distribution which allows you to specify install location when you execute it.

cheers,
Andy
---
Andy Clement
SpringSource

Hi Andy,
thanks very much for the response.
Unfortunately the problem is not just in WinRar - Windows itself seems to have this limit baked into it in some places - when copying the STS folder we get errors and the copy does not work.
Obviously this is not a huge issue - we can replicate on to other machines with a zip file - it just doesn't show the product in its best light when the client's backup software starts blowing up on it!
Cheers

See also http://discuss.joelonsoftware.com/de...oel.3.57363.31, http://stackoverflow.com/questions/2...s-xp-and-vista, http://msdn.microsoft.com/en-us/libr...47(VS.85).aspx

Hi,

Yes, I see those path issues on my Windows box occasionally. I guess because of the tools I normally use to unpack these things, I fail to notice sometimes when a new problem has been introduced (a new module with a long name). That's why I mentioned we are actively addressing this - in the particular case you showed we will move to packing the src for that module into an internal zip rather than including it in STS in an 'unpacked form' - not sure I'm making total sense there, but I know what I mean :)

cheers,
Andy

http://longpathtool.com/

Long Path Tool helped me in this situation. http://PathTooDeep.com :)

If your folder destination path is too long(more than 255 characters in Windows),you can came across a long path error.You can fix it with additional softwares like Long Path Tool.
http://PathTooDeep.com
I hope that it will help you!
Good luck!
Cheers!