Bug 7210 - Moving Classes Does Not Update the Packages View
Summary: Moving Classes Does Not Update the Packages View
Status: RESOLVED DUPLICATE of bug 7070
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows NT
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Erich Gamma CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-31 15:46 EST by Jeff Butler CLA
Modified: 2002-01-09 18:05 EST (History)
1 user (show)

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 Jeff Butler CLA 2001-12-31 15:46:37 EST 
Moving a class to a different package does not properly update the packages 
view in the Java perspective.  To reproduce:

1. Create a new java project
2. Create package a.b.c
3. Create class a.b.c.Foo
4. Right click on Foo, select "Move..."
5. Select a different package (either a, or a.b), press OK

You will still see Foo in a.b.c package, but you won't be able to open it.  
Neither of the other packages will appear because the UI thinks they are still 
empty packages.  BTW - the file does get moved properly in the file system, 
just the UI is not updated.

Circumvention - stop and restart eclipse, then everything is OK.
Comment 1 Tod Creasey CLA 2002-01-02 09:41:30 EST 
Moving to JDT
Comment 2 David Weitzman CLA 2002-01-03 22:17:55 EST 
This should have a higher priority than 3.  I've been moving a lot of files 
while refactoring recently (and I don't think that's an unusual thing to do) 
which means I have to restart Eclipse more than I'd like to.  A simple and 
ordinary thing like moving a file should not make that file inaccessable.
Comment 3 Erich Gamma CLA 2002-01-09 18:05:26 EST 
duplicate, the bug got fixed in 20020108

*** This bug has been marked as a duplicate of 7070 ***