Community
Participate
Working Groups
As a result of the team-private flag not causing a delta when it is set, there are some cases where setting folders as team private won't hide them from the UI as the user would expect. There are some common scenarios where a user may (depending on the order of delta traversal) see this behavior: 1. A user has an existing CVS project outside of Eclipse. By creating the project in Eclipse to point to the existing location the project's contents will be brought into Eclipse and the CVS folders will be marlked as team-private but other delta listeners will not know this. As a result, the user will have to close views or restart the workbench to have the CVS folders filtered. 2. A user performs CVS command line operations outside of Eclipse that results in new CVS folders. From Eclipse the refresh local will bring in the new folders and they will be marked as team-private. But as in 1, they may appear in the UI. There is no plan to be fix this.
Re 1: Should setting it to team-private result in a delta that on the surface appears to be a remove? Re 2: I will discuss with JW. There is work underway to auto-refresh projects by looking for out of date files in a background process and doing a refreshFromLocal. This would mean the user wouldn't even get a chance to do a special "Refresh CVS" operation.
later
Reopening
*** This bug has been marked as a duplicate of 21128 ***