Bug 1837 - [Import/Export] import of password protected zips fails (1G470E4)
Summary: [Import/Export] import of password protected zips fails (1G470E4)
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All Windows NT
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Tod Creasey CLA
QA Contact:
URL:
Whiteboard:
Keywords: investigate
Depends on:
Blocks:
 
Reported: 2001-10-10 22:20 EDT by Martin Aeschlimann CLA
Modified: 2002-08-29 14:10 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Aeschlimann CLA 2001-10-10 22:20:19 EDT 
MA (11/10/00 11:22:27 AM)
	1. import content from a password-protected zip (for Example startupsrc.zip from the eclipse-vame-0.011release
	2. files are all created but empty. error message is not very helpful
NOTES:

EG (11/13/00 2:42:00 PM)
	zip importer is owned by the desktop

SA (4/10/2001 2:34:28 PM)
	This is still a problem. The actual error message when reading from
	the zip file is "java.util.zip.ZipException: too many length or distance symbols"
	which does not give any information to the real problem. There does not
	seem to be any api on ZipFile and ZipEntry to query whether the zip
	file is password protected or not.

SA (5/1/2001 4:40:50 PM)
	About the only way we can handle this is if we implement our own zip file reader.
	We would need access to the zip file format doc... The other solution is to update
	the error message we display with some possible reasons (blah blah blah...make
	sure the zip file exist, none of the files in are password protected, etc)

	Moving to Features folder
Comment 1 DJ Houghton CLA 2001-10-24 06:47:43 EDT 
PRODUCT VERSION:
	eclipse-vame-0.011
Comment 2 Kevin Haaland CLA 2001-11-22 06:21:05 EST 
Deferring until development resources become available to consider this 
enhancement.
Comment 3 Randy Giffen CLA 2002-08-01 12:04:27 EDT 
Reopened for investigation
Comment 4 Tod Creasey CLA 2002-08-29 14:10:23 EDT 
in 20020827 you now get an individual "could not read source" error for every 
file.