Bug 3624 - rename, delete operations should check read only state of resource (1GD2B0V) [ccp]
Summary: rename, delete operations should check read only state of resource (1GD2B0V) ...
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All Windows 2000
: P4 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on: 4210 6052 6054 6055 6058
Blocks:
  Show dependency tree
 
Reported: 2001-10-10 22:58 EDT by Erich Gamma CLA
Modified: 2009-08-30 02:04 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erich Gamma CLA 2001-10-10 22:58:10 EDT
EG (5/30/01 9:29:33 AM)
	for June at least delete should check the read only state

NOTES:

TM (5/30/2001 15:52:01)
	What about move?

TM (5/30/2001 16:17:11)
	Major change: we're not looking traversing containers when they're java elements. We would have to introduce that.
Comment 1 Martin Aeschlimann CLA 2001-10-16 11:16:08 EDT
moved to 'active'
Comment 2 Erich Gamma CLA 2001-11-10 12:24:51 EST
this is now covered by refactoring.
pls check whether the read-only cases are now handled properly.
Comment 3 Adam Kiezun CLA 2001-11-15 05:15:13 EST
marked as dependent on 4210
some additional issues will have to be resolved though
after 4210 has been fixed

Comment 4 Adam Kiezun CLA 2001-11-15 05:16:25 EST
fixed incorect bug number
Comment 5 Adam Kiezun CLA 2001-11-19 06:36:27 EST
details:
1. files
 delete: OK should ask and asks
 rename: WRONG: should be enabled and ask the user
          for non-java files - is disabled
          for cus (see bug#4210)
 copy: WRONG: non java ok
          cus (see bug#4210)
 move: WRONG for cus (see bug#4210)

2. packages
 delete: OK
 rename: WRONG: renaming does not ask and removes the read-only flag
         WRONG: if a read-only cu exists in package - exception (bug#4210)
 copy: WRONG: loses the read-only flag
 move: WRONG: loses the read-only flag

3. folders
delete: OK
rename: WRONG: disabled
copy: WRONG: loses the read-only flag
move: OK

4. source folders
delete: OK
rename: OK - information on the refactoring error page
copy: WRONG: copying loses the read-only flag
move: OK

5. projects
delete: OK
rename: OK - information on the refactoring error page
copy: n/a
move: n/a

summary: 
a. 4210 (copy/move read-only compilation units (1GK1KJM))
b. 6052 (rename disabled for read-only resources)
c. 6053 (copy loses read-only flag)
d. 6054 (renaming a read-only package resets the read-only flag)
e. 6055 (rename a read-only package does not issue a warning)

marking the bug as dependent on all of the above
Comment 6 Adam Kiezun CLA 2002-09-18 04:08:07 EDT
this report is simply a bucket for other 'read-only'-related reports
changing resolution to 'remind'
Comment 7 Denis Roy CLA 2009-08-30 02:04:58 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.