Bug 3026 - Problems importing from password encrypted Zip (1GDXUT5)
Summary: Problems importing from password encrypted Zip (1GDXUT5)
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: John Arthorne CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 22:48 EDT by DJ Houghton CLA
Modified: 2001-11-01 10:22 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description DJ Houghton CLA 2001-10-10 22:48:05 EDT
I tried to import the source from JCore into my workspace. I got a problem report at the
	end saying that there was a lot of problems trying to write files.

	I believe that this was because the zip file was password encrypted. I was not
	prompted to enter a password to open the file.

NOTES:
	EJP (5/28/01 12:16:54 PM)
		1 - JDK does not have support for zip with password.
		2 - Did not find a way to know if a password was used or not to abort the operation before starting it.
		3 - A ZipException is thrown because zlib can't deflate the file contents.
		4 - The message in the ZipException does not help much: "incomplete dynamic bit lengths tree"

	EJP (5/28/01 12:28:23 PM)
		The only thing that can be done here is to show a better message to the user.
		The current message: "Could not write file" is too poor.
		Moving to core since this message is created in:
			 in org.eclipse.core.internal.localstore.FileSystemStore
		The code is handling read and write exceptions in the same block and assuming 
		the problem happened when writing.
		
JM (6/4/2001 3:17:22 PM)
	Consider updating the messages.

JM (05/06/2001 7:11:34 PM)
	Defer
Comment 1 DJ Houghton CLA 2001-10-24 06:41:25 EDT
PRODUCT VERSION:
	0.108 JRE on Win98

Comment 2 John Arthorne CLA 2001-10-31 18:28:27 EST
Improved the error reporting so that it indicates an error occurred during read 
rather than write.  I don't think it's much more helpful than before, but not 
much else we can do.  Moving to closed.
Comment 3 Rodrigo Peretti CLA 2001-11-01 10:22:33 EST
Fixed in v207