Bug 279714 - team - synchronize should synchronize the resource instead of throwing an error "resource out of sync with filesystem"
Summary: team - synchronize should synchronize the resource instead of throwing an err...
Status: RESOLVED DUPLICATE of bug 238762
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.4.1   Edit
Hardware: All Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-09 18:30 EDT by Missing name CLA
Modified: 2009-06-10 04:03 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Missing name CLA 2009-06-09 18:30:21 EDT
team synchronize gives "resource ouf of sync with file system" error. it would be nice if eclipse would solve that problem by its own if it already knows what it is instead of surprising a puzzled user. in this case: synchronize.
Comment 1 Szymon Brandys CLA 2009-06-10 03:51:23 EDT
"resource ouf of sync with file system" in this context means that resources in your workspace are not in sync with underlying files. We can't do the synchronization automatically since it could trigger builders or start any other facilities being aware of resources' changes.
Comment 2 Tomasz Zarna CLA 2009-06-10 04:03:17 EDT
There is an auto-refresh preference[1] which will keep your workspace in-sync with the file system. If this option is turned on then the workspace resources will be synchronized with their corresponding resources in the file system automatically. However, as Szymon mentioned in comment 1, this can potentially be a lengthy operation depending on the number of resources you have in your workspace. 

Another approach could be to allow to refresh directly from the error dialog[2]. This is probably the most convenient solution at the moment.

[1] General > Workspace > Refresh automatically
[2] bug 238762


*** This bug has been marked as a duplicate of bug 238762 ***