[#JRA-7143] Can't unzip jira into directory with a long path name

JIRA

Can't unzip jira into directory with a long path name

Created: 24/Jun/05 02:22 AM Updated: 20/Nov/06 08:27 PM

Component/s:

Installation

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Environment:

Windows

Participants:	Anton Mazkovoi [Atlassian], Claude Betancourt, Jeff Turner [Atlassian], Leon Zandman, Neal Applebaum and Nick Menere [Atlassian]
Since last comment:	88 weeks, 3 days ago
Labels:

Description

« Hide

Microsoft's Win32 API maximum file path length (MAX_PATH = 260
characters; see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/fs/naming_a_file.asp). This is confirmed by the fact that if I extract
your ZIP file to my root drive (I:) everything goes just fine.

The longest path in your ZIP file is 186 characters long:
"atlassian-jira-professional-3.2.1-standalone\atlassian-jira\WEB-INF\cla
sses\com\atlassian\jira\web\action\admin\issuefields\screens\ConfigureFi
eldScreenScheme$DefaultIssueOperation.class". This means that you cannot
extract the ZIP file to a destination path that exceeds 74 characters
(260 - 186 = 74). I got the error when I wanted to extract it to a new
folder on my desktop. The total length of the path of that folder was 87
characters, which was too long.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Neal Applebaum - 24/Jun/05 06:55 AM

Hey Nick, just to make sure to check the obvious, are you by chance using Windows XP's built-in unzip tool?
http://www.atlassian.com/software/jira/docs/v3.2/install.html#avoid_xp_unzip

[ Permlink | « Hide ]

Leon Zandman - 27/Jun/05 01:35 AM

I was the one that stumbled on this bug and reported it to Nick. He included only a small part of my e-mail describing this bug in this issue's description. I used WinZip 8.0 (3105), but also confirmed this behaviour using WinRAR and 7-ZIP. I think it's not the ZIP software that's causing this problem, but it's Windows itself.

[ Permlink | « Hide ]

Claude Betancourt - 06/Jan/06 04:57 PM

I am not sure what other updates have been posted about this bug, but I did not encounter this problem unzipping JIRA 3.4.2 standalone on Windows 2003 using WinRAR 3.51.

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 08/Jan/06 10:11 PM

Claude,

Thanks for the information. Can I confirm that you have unzipped JIRA into a path that was longer than 74 characters?

Maybe WinRAR 3.51 uses the Unicode functions for file system access mentioned in:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/fs/naming_a_file.asp

Thanks,
Anton

[ Permlink | « Hide ]

Leon Zandman - 09/Jan/06 01:28 AM

I also tried WinRar when I originally reported this issue to Nick. It also failed with WinRar. I don't know what version of WinRar I was using a the time, though.

[ Permlink | « Hide ]

Claude Betancourt - 30/Jan/06 10:09 PM

That's correct Anton, I checked the longest path reported above. My version is 3.4.2 professional.

"atlassian-jira-professional-3.2.1-standalone\atlassian-jira\WEB-INF\classes\com\atlassian\jira\web\action\admin\issuefields\screens\ConfigureFieldScreenScheme$DefaultIssueOperation.class"

Claude.

[ Permlink | « Hide ]

Jeff Turner [Atlassian] - 08/Nov/06 02:31 AM

If we zipped the .class files and .vm files, we could pretty much eliminate this problem.