Bug 73099 - [classpath] user libraries keep missing jar file contents.
Summary: [classpath] user libraries keep missing jar file contents.
Status: RESOLVED DUPLICATE of bug 97524
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.1 RC2   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-01 16:57 EDT by Quynh Dang CLA
Modified: 2005-06-10 04:32 EDT (History)
1 user (show)

See Also:

Attachments
exported user libraries file (2.79 KB, text/plain)
2004-09-01 16:58 EDT, Quynh Dang CLA 		no flags Details
View All 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 Quynh Dang CLA 2004-09-01 16:57:19 EDT 
I created user libraries (about 6), each contains a number of jar files, from 2 
to 7 or 8.  I then exported these user libraries to an export file for 
sharing.  I noticed after exporting to a new workspace, one of the user 
libraries will be empty or reset.  Even after I added back the jar files, 
restarting Eclipse will reset the user library to empty.  This is very annoying 
since I have to keep readding the jar files back to the user library. 

In addition, different projects using the same user libraries will have a 
misbehaved user library.
Comment 1 Quynh Dang CLA 2004-09-01 16:58:44 EDT 
Created attachment 14334 [details]
exported user libraries file
Comment 2 Philipe Mulet CLA 2005-04-07 09:26:13 EDT 
Deferring post 3.1
Comment 3 Frederic Fusier CLA 2005-06-10 04:24:27 EDT 
Reopen to set as duplicate
Comment 4 Frederic Fusier CLA 2005-06-10 04:27:36 EDT 

*** This bug has been marked as a duplicate of 97524 ***
Comment 5 Frederic Fusier CLA 2005-06-10 04:32:15 EDT 
Set as duplicate although I'm not really sure it's really the case...
There's no API methods in JDT/Core to export user libraries, so this is
performed by JDT/UI specific code. I guess it has been fixed since this bug was
opened.

I didn't move this bug to JDT/UI for confirmation due to the fact that Brian let
us know this issue is fixed in RC1...