Bug 252571 - [buildpath] External folder appears empty after workspace move
Summary: [buildpath] External folder appears empty after workspace move
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.5 M4   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-29 08:38 EDT by Jerome Lanneluc CLA
Modified: 2018-12-18 03:19 EST (History)
1 user (show)

See Also:


Attachments
Proposed fix (6.22 KB, patch)
2008-11-25 05:23 EST, Jerome Lanneluc CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Jerome Lanneluc CLA 2008-10-29 08:38:03 EDT
I20081029-0100

1. Start a new workspace on "d:\temp\test"
2. Create a Java project "Test"
3. Add a non-empty external class folder to the build path of "Test" (e.g.
"d:\temp\lib")
4. Shutdown
5. Rename "d:\temp\test" to "d:\temp\test2"
6. Start Eclipse on this new workspace
Observe: The external folder node in the Package Explorer appears empty
Comment 1 Jerome Lanneluc CLA 2008-10-29 08:40:37 EDT
Variation on this scenario:
1. Start a new workspace on "d:\temp\test"
2. Create a Java project "Test"
3. Add a non-empty external class folder to the build path of "Test" (e.g.
"d:\temp\lib")
3a. Open a .class file from the external folder in a class file editor in Eclipse
4. Shutdown
5. Rename "d:\temp\test" to "d:\temp\test2"
6. Start Eclipse on this new workspace
Observe: The class file editor is not correctly restored due to an exception.
Comment 2 Jerome Lanneluc CLA 2008-11-25 05:23:00 EST
Created attachment 118646 [details]
Proposed fix

Note that there is no regression test as one cannot move the workspace in
tests.
Comment 3 Jerome Lanneluc CLA 2008-11-25 10:11:48 EST
Fix released for 3.5M4
Comment 4 David Audel CLA 2008-12-09 05:23:10 EST
Verified for 3.5M4 using build I20081208-1800