Community
Participate
Working Groups
I recently had a situation where I wanted to view a co-worker's code staging area and compare it with mine, so I created a linked folder to point to it. Everything worked fine until I almost started modifying his code by accident. I don't have control over the target's file permissions but I want control over my usage of the target. So I'm asking for an option that, when a linked resource or folder is created, I can tell Eclipse that this is read only even if the file permissions would normally allow writes. That way Eclipse can prevent accidental modifications to that resource or any files under that folder. Modifications would include editing, renaming, and deleting. Since this is an enhancement request, post 3.0 is fine if you want to 'Later' it.
Not for 3.0
Reopening now that 3.0 has shipped
This seems to be related to bug 88215.
Bug 69181 also sounds like a similar problem.
*** Bug 6622 has been marked as a duplicate of this bug. ***
This message is part of a mass update on bugs that have been reviewed for several releases, but not fixed. The bug is legitimate, but not a priority. Marking P5. Patches would be entertained.
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
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.