Closed timja closed 15 years ago
Most applications creating ZIP files just add a slash ("/") to a file path to
indicate that this path refers to a directory.
Some unzippers (like Window's built-in compressed folder feature) require in
addition, that a special directory bit is set for a ZIP file entry - otherwise
it's regarded as a file.
Code changed in hudson
User: : swiest
Path:
trunk/hudson/main/core/src/main/java/hudson/FilePath.java
http://fisheye4.cenqua.com/changelog/hudson/?cs=16278
Log:
[FIXED JENKINS-3294] ZIP archives created by Hudson are now rendered properly in Windows' built-in "compressed folder" views.
Code changed in hudson
User: : swiest
Path:
trunk/www/changelog.html
http://fisheye4.cenqua.com/changelog/hudson/?cs=16280
Log:
JENKINS-3294 Noting fix.
(From the users' mailing list
Flominator wrote on 16.03.2009 13:27:
> I've been experimenting with Hudson some weeks and didn't find any problem,
> that I wasn't able to solve by using the web. But then came this one:
>
> We archive artifacts of our MSBuild + InstallShield build tasks. You can
> download either specific files or whole directories from within Hudson. When
> downloading directories a zip file is generated.
>
> When you try to open the zip file as "compressed folder" in Windows
> explorer, it shows the directory. But it also shows an empty file that has
> the same name as the folder.
>
> This file prevents windows from extracting the folder: There is one for
> every directory in the file. When you extract the whole zip file windows
> cannot extract the folders because the files are extracted first and cannot
> be overwritten.
>
> When using 7zip everything works fine, but since not all of our developers
> have that installed, we would really like to be able to use windows
> explorer.
>
> Is this a known problem? Are there any solutions?
Originally reported by swiest, imported from: ZIP archives created by Hudson do not render properly in Windows Explorer