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

Bug 364014

Summary:	[ltk] ReadOnlyResourceFinder#hasReadOnlyResourcesAndSubResources could check if .project is read-only
Product:	[Eclipse Project] JDT	Reporter:	Szymon Brandys <Szymon.Brandys>
Component:	UI	Assignee:	Markus Keller <markus.kell.r>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	daniel_megert, deepakazad, markus.kell.r
Version:	3.7
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Szymon Brandys

2011-11-17 06:26:44 EST

If we are removing linked resources, we actually modify .project file. ltk should check if .project is read-only and if it is true, we should ask to make .project writable or cancel the operation. I guess that the right place is ReadOnlyResourceFinder#hasReadOnlyResourcesAndSubResources and #confirmOperationOnReadOnlyElements which ignore linked resources at the moment.

Comment 1 Szymon Brandys

2011-11-18 05:55:42 EST

On the other hand, for non-experienced users it may be not obvious why to modify .project permissions to delete a linked resource...

Comment 2 Eclipse Genie

2019-10-13 17:57:59 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.