Community
Participate
Working Groups
Build ID: I20070621-1340 Steps To Reproduce: 1.Mark Resource as read only. 2.Open Editor with doble click on resource. 3.Change content and save. 4.File is saved and not read only more. More information:
Which editor?
We have tested with JavaEditor and PythDev.
Tested in 1101 and works as expected, you are prompted for a read only file. This is unlikely to have changed since 0621. However, Team repository providers can override this behaviour. Which are you using? Please report this bug to them.
We use CVS.
It works as expected in 3.3.
I put generated sources in .cvsignore and mark it as "read only". I think, it is not work as expected, if I can change protected sources that not under CVS control without any warnings!
(In reply to comment #6) > I put generated sources in .cvsignore and mark it as "read only". > I think, it is not work as expected, if I can change protected sources that not > under CVS control without any warnings! What it meant was, "working as expected given the information we have at hand". So to be clear, the case then is (?): 1. create a file foo.txt 2. add it to .cvsignore 3. set foo.txt to read-only 4. open editor... 5. change content... 6. save...
Yes, a bit sophisticated is a lot of .java files in src directory. The src directory is added to .cvsignore.
Created attachment 82277 [details] CVS settings How can I change behavior for read only files under CVS control, if the settings are disabled?
Or, if I misunderstood this feature: How can I change CVS settings so, that the user become always a warning if he trying to change or to override readonly files (even if this files stay under CVS-control)?
As mentioned by Kevin in comment 3, overriding the read-only bit by repository providers is an expected behavior -- see bug 67122 and bug 34793. Currently, we don't have the manpower to address it, but if you have strong feelings about this issue you can provide us a patch.
Ok, overriding the read-only bit by repository providers is an expected behavior. But if this file is not under CVS control (entered in .cvsignore), this behavior is wrong. Unfortunately I havn't path for this issue.
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.
