177584 – Confirm Project Delete / "Do not delete contents" still appears to prepare to delete contents

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 177584 - Confirm Project Delete / "Do not delete contents" still appears to prepare to delete contents

Summary: Confirm Project Delete / "Do not delete contents" still appears to prepare to...

Status:	RESOLVED DUPLICATE of bug 177119

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	UI (show other bugs)
Version:	3.3
Hardware:	PC Windows 2000

Importance:	P3 major (vote)
Target Milestone:	---
Assignee:	Platform-UI-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2007-03-15 12:20 EDT by Mark A. Ziesemer
Modified:	2007-03-15 15:52 EDT (History)
CC List:	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 Mark A. Ziesemer

2007-03-15 12:20:20 EDT

Build ID: I20070209-1006

Steps To Reproduce:
1. Within the Package Explorer, select a project, then delete.
2. The "Confirm Project Delete" confirmation appears, with either "Also delete contents under ...", and "Do not delete contents" options.  Leave "Do not delete contents" selected.
3. Click Yes.

I'm then presented with a "Confirm Resource Delete" confirmation dialog, with "'.classpath' is read only.  Do you still wish to delete it?"  This is after I selected "Do not delete contents above".

The only way to proceed is to click "Yes To All" on the "Confirm Resource Delete", which actually does NOT delete the files, but allows the project to be removed.  (But this is NOT a work-around that should be advertised, as it would be a very bad habit to get into.)

An alternative is to first close the the desired projects, then delete.

Comment 1 Eric Moffatt

2007-03-15 15:52:35 EDT

Marking as a dup of bug 177119 since its repro scenario is clearer...


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