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

Bug 77569

Summary: [Watch/Edit] Project not set read-only after a share of existing project
Product: [Eclipse Project] Platform Reporter: Roger Stoffers <roger.stoffers>
Component: CVSAssignee: platform-cvs-inbox <platform-cvs-inbox>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: P4 Keywords: helpwanted
Version: 3.0.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows NT   
Whiteboard:

Description Roger Stoffers CLA 2004-11-03 03:37:06 EST 
When the watch/edit sync is turned on and sharing a project that already exists 
in CVS, the readonly attibutes are not set on the local filesystem.

After unsetting/setting the watch/edit flag, local readonly attributes are 
initialized.

Shouldn't this last step be unnecessary?
Comment 1 Michael Valenta CLA 2004-11-03 07:49:34 EST 
Yes, the share should handle that.
Comment 2 Anthony Park CLA 2005-04-18 19:32:30 EDT 
This is also a problem when adding new files to an existing project.
Comment 3 Jean-Yves TOUMIT CLA 2005-04-19 07:40:16 EDT 
I have the same problem with newly created files.
To reproduce this, create a new file in a shared project. Commit it. It is *not*
set read-only once the commit has been performed, so it will not force an edit
the next time it's modified, which is really bad. You have to set the Watch/Edit
state off and then on again on the project to reinitialize read-only states
correctly on the project.
Comment 4 Michael Valenta CLA 2005-04-19 08:43:38 EDT 
Regarding comment 2 and comment 3, this problem was fixed in 3.1
Comment 5 Michael Valenta CLA 2005-05-31 14:28:07 EDT 
There is currently no plan to address this item.
Comment 6 Denis Roy CLA 2009-08-30 02:25:07 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.